I've spent many career years in sysadmin / process automation for manufacturing companies, and LOTO is one of many pieces of proper procedure and process that really impresses me about that industry. I worked at a big steel recycling plant, and the zero tolerance effort put toward safety and generally ensuring that this type of stuff was upheld was impressive. Not locking out a machine, or forgetting your lock on a machine was a fireable offense with like, one warning I think. You certainly didn't want to be the guy who was working on a machine that morning, and left your lock on it when you went home while someone else was working on it. They'd call you and get you out of bed real quick if it meant the machine couldn't start up because your lock is on there and you weren't accounted for.
SRE's and operations people can pick up good habits from manufacturing gigs. A lot of the same concepts like uptime, good documentation, procedure, discipline are really important to the business at all levels. When lives are at risk good companies put a large sum of time and money in making sure everyone is on the same page.
I was a VMware admin primarily for years in engineering shops and everywhere I worked constantly had issues with resource allocation, which team had the most resources deployed, who had the most idle vCPU and memory running...
At one company pretty much my sole job for 2 days a week was to look over utilization by team, shutdown idle VM's and check for any that were provisioned with too many resources. I'd have to e-mail the team, power them down and resize the resources and boot it back up, etc.
I automated all that with scripts, from the team e-mails with a nice HTML table report of the pending changes to actually running the operations to resize and power off the machines. I was pretty proud of all that work.
I feel like that makes it readable. Even people who don't know PS very well can read cmdlets and pretty much know what's going on if you use the full verbose cmdlets.
I get sick of all the downplaying that PowerShell gets. I find interacting with the console a breeze, and just as usable as Bash. I can easily perform an ad-hoc API call into an Object, explorer it and export it into a well formatted .csv file for a report in minutes.
We use it in tooling for tons of things that would otherwise be done in Python and have no issues. Especially once you get it set up on Server Core and run the jobs in Cron.
I just don't get all the negativity towards it. There's a reason so many vendors are providing great PS modules for their products: VMWare, AWS, etc.
SRE's and operations people can pick up good habits from manufacturing gigs. A lot of the same concepts like uptime, good documentation, procedure, discipline are really important to the business at all levels. When lives are at risk good companies put a large sum of time and money in making sure everyone is on the same page.