Hmmm.
Yes, I tend to agree. If an admin's 'toolkit' of IT security options is via shell history files, then they have a long way to go......
On the other hand, we are here to guide them on the path.
It is a bit hard for folks with limited experience to see all the options AND they may work in an environment with limited resources to collaborate on these issues.
There are many legitimate system adminstrators with mult-user systems where accountability is critical to the mission. This is not 'spying' on the users because the systems are IT resources that belong to the company and the actions of users on those systems often require accountability. This is always true when the system application is insured, requires certification, and a myriad other professional operational IT system requirements.
Are we off topic yet?