jiraticketmach
This is something that has always amazed me.
Your typical tech worker does a lot of unpaid overtime under the guidance of a manager whose only merit to management is being friends with someone. It also has to retrain him/herself for free on it´s own spare time and by the time it reaches 35/40 it tends to be let go by not raising his/her salary anymore or by putting him/her in lower status position. (Not to mention working as a contractor for years, etc.). These are the kind of problems unions are expected to fight for.
But every time someone mentions unions they go after the salary cap, time of service, etc, discourses.
For example: your typical big bank has hundreds or thousands of teams (both internal and through professional services companies) developing all kinds of applications under different technologies/hardware.
In this case due to domain/organizational scale it is not feasible to have a mono repo (or 2, or 3) with a giant codebase.
And as a result the typical situation is an expensive hell full of code duplication, ad-hoc integration methods, nightmarish deployments and such.
Microservices are helpful in situations like this (even if they are not perfect).
But for a company with a couple of development teams and a domain that can be understood almost entirely by a couple of business analysts, it´s overkill.
Believe me, being able to push yourself beyond what a younger fellow can it's a sad excuse for a competitive advantage. I do know.
It's sad to see this kind of articles, as if ability to resist burnout is a valuable quality. Work-life balance be damned...
If you were to take an important exam will you just read the text from start to finish or will you also take notes, analize, discuss, memorize, etc?