Also, `jc` automatically selects the correct /proc/file parser so you can just do `jc /proc/meminfo` or `cat /proc/meminfo | jc --proc` without specifying the actual proc parser (though you can do that if you want)
The guy handling the affairs describes his experience:
"I have over 40 years of legal and restructuring experience. I have been the Chief Restructuring Officer or Chief Executive Officer in several of the largest corporate failures in history. I have supervised situations involving allegations of criminal activity and malfeasance (Enron)."
Then states:
"Never in my career have I seen such a complete failure of corporate controls and such a complete absence of trustworthy financial information as occurred here. From compromised systems integrity and faulty regulatory oversight abroad, to the concentration of control in the hands of a very small group of inexperienced, unsophisticated and potentially compromised individuals, this situation is unprecedented."
Once my wife learned of my plans, the requests for custom pieces started rolling in. Knowing that whatever I build has an eager recipient awaiting it is rocket fuel for motivation.
And since it's my wife asking for it, it's easier to justify buying the tools I "need".
I've grown my tool collection repeatedly this way :)
Check out the author. For those not in the know, Kahan was the driving architect behind IEEE 754 -- pretty much the basis of all computer floating point now.
See https://en.wikipedia.org/wiki/William_Kahan
I remember seminars at Berkeley where equipment manufactures show up to talk about their gear and Kahan would sit in the front row and grill them over their floating point implementations.
You're probably right, this program looks great and reflects how the industry has changed since A+ towards cloud-based systems. Shame though - people tend to come to IT because they like playing with their computer and A+ was a natural stepping strong from that to administrating a computer. It was like the Hobby->JuniorProfessional stepping stone.