Literally no engineers were allocated to the issue and majority of the project.
20% of the time I work on novel unforseeable issues. R&D and future tech stuff.
80% of the time its culture, professionalism, and generally "are you fucking serious" issues.
I've dealt with literally every situation you've described however. Just because this particular reason was that there were no engineers, you could swap in any other situation and still have a true story.
All writ{ers,ing} {are,is} emotionally soluble. And sometimes you need to unload before you can think clearly and articulate with perfect moderation. It's fine.
The article and writing was very good. The rant sections could have devolved several orders of magnitude further, that wasn't the end of the world IMO.
I got some major general-worldview TILs about engineering from the parts that talked about experience levels.
The bits you said could be their own articles, and/or which you said you could go on about... I hope to read about those in followup posts. :D
Agreed - great article. That said, I think most authors of books like the one we're all imagining have support (in the form of friends and colleagues) in addition to an editor. I don't want to pressure you to write a book, but please don't let your own criticism of your writing abilities get in the way of a book.
I’d help in whatever way you’d like. My dream is to make a company engineers love to work in. The chance to learn from whatever you share would be amazing.
'It's funny how small scale engineering problems are rooted in code and large scale engineering problems are rooted in people.'