I suspect that tech management & executive culture has learned & become accustomed to exploit the mental health of their employees. Software and tech are stereotypically jobs well suited to neurodiversity and ADHD, and those people are prone to hyperfocus & long hours and may benefit from tight timelines. If management just gets used to recruiting for autism/adhd, then develops management strategies that work well with that population, it’s going to be difficult as the field matures and attracts more neurotypical people.
I used to tell my mentees that no one was going to explicitly tell them that 10, 12, 14 hour days were mandatory. That long hours were not a metric for success. It was that they would be competing for jobs with people who really did want their life to be their job and would happily spend that much time working, because that’s all they want to do. It’s only when the pool of available jobs grows beyond the number of those obsessive workaholics that they have to start hiring people who have any interest in work-life balance or collective bargaining.
This is one of my pet peeves with containerized services, like why would I want to run three or four instances of mariadb? I get it, from the perspective of the packagers, who want a ‘just works’ solution to distribute, but if I’m trying to run simple services on a 4 GB RPi or a 2 GB VPS, then replicating dbs makes a difference. It took a while, but I did, eventually, get those dockers configured to use a single db backend, but I feel like that completely negated the ‘easy to set up and maintain’ rationale for containers.