So I like the work on this article to deep dive into some of the phenomena but it doesn't really give a way to cope with the exhaustion. I think knowing that would be more helpful so that the load of the career doesn't cause burnout.

A lot of software engineering work is meaningless and you know it. It’s working in a team at the speed of the slowest member to duplicate some trivial cross-functional layer that’s already been solved thousands of times, it’s telling yourself this is job security until the company notices there’s two people getting paid for every one person’s work, it’s wondering why you have to look at another screen to read about another screen to turn back to another screen.