As a kid, I aspired to be a programmer. As an adult, I succeeded, and I stuck around for a good long while. There are a lot of reasons to like working tech, obviously: the salary, the flexible working environment, the prestige, the opportunity to build products that real people use, the chance to play with new technology, and of course working with occasionally brilliant colleagues. I tried to convince myself that th…
> I was spending more time wrestling with package managers, version conflicts, obtuse configuration files, pointless deadlines, egotistical colleagues, and almost zero time solving interesting problems on products that I care about. That squares with my experience of software development. It's like being a furniture maker but spending 80% of your time fixing your goddamn hammer because it keeps breaking and no better…
This is something that you're supposed to know on the first day after you finish apprenticeship.
In the modern tech industry you need authorization from your product owner/manager and engineering manager just to build a new tool or abstraction to automate or speed up your own job, because god forbid you do anything that's not in JIRA.