| If I'm reading this right, the crux of the issue was overworked engineers and unproductive meetings that got heated between experts? And the resultant stress led to brain damage? Personally, I don't know any software teams that aren't understaffed at best. Any project that has multiple stakeholders is going to have some meetings that feel unproductive with key leaders arguing for their best interests. That's just the natural order of collaboration. These are the kinds of posts that remind me how privileged high-skilled software engineers are. I am the first in my family to not work in some form of construction and can't help but imagine how someone like OP would fare in that environment. > I spent the next couple years unemployed, working with my physicians to try and recover my health while occasionally writing code. I’m happy to report that I’m partially recovered at this point and being paid to work on open source, but I’ll never be the same. Being able to take off 2 years to attend to personal health is a luxury pretty exclusive to tech (insofar as how available/attainable it is). |
My point is, I don't think these comparison judgement are useful. Ever heard: "can't compare two people's pain"?
Think about the purpose of your comment? What's the end goal? To convince people nothing should be done about anything and for everyone to just suck it up? Seems that's a bad attitude to be honest.
If your family's construction work environment is toxic and treats them badly, you should be complaining about it and bring attention to it so hopefully we can all demand better for them. Similarly here, someone stepped up to try and raise the standards by pointing out at real issues faced in some organizations that fail on all front, fails to deliver to the business, the customer, the employees, it's worth talking about in my opinion. How else you get anything to become better otherwise?