And then there was code documentation. The engineers programming the company’s products had standards to follow, and code reviews to attend. On the lower floor of the building, the IT engineers, mostly by the time I left Indians, immune to all layoffs, even more so than the few blacks who worked there, these guys didn’t have to do chit, and didn’t, not a single word of documentation in their Java and SQL code, and their (white) management didn’t care, resisted calls for standards, disdained talk of code reviews. I was in those respects lucky, working in IT but coding for Engineering, having to document my perl code, and going through code reviews with the Engineering group which also produced software for Engineering, a weird arrangement, having to do with competing personnel budgets and other such political nonsense.
LOL... I remember being told many years ago that properly written code was self documenting and did not need comments.
I occasionally cranked out some very elegant code, with comments, but when looking at it some years later I often wondered "what on earth was I thinking that day?" Everything makes great sense at the time, not so much after a year or two.