"I tried prioritizing my work, focusing on the things I felt the most passionately about, but when I tried to work on the projects at the top of this list I couldn't summon any energy. Yet I spent hours and hours thinking obsessively about the ultimate point of my work."

I mean, heck, the guy said he was reading 50 (no doubt challenging) books a year on his work. That's insane.

It's pretty simple: you can't work at an insane pace forever, and eventually your subconscious will rebel and stop working with you.

In my case, it felt like my intentions and actions were connected by a plastic gear, and I had spent so many years jamming that gear as hard as I could that it stripped the teeth off of it. My intentions could spin as hard as they wanted to, but eventually I just found it impossible to do anything.

I think there are versions of this where the issue is not pace or volume of work, but rather “meaning” or greater societal impact.

I used to work at a place that gathers a ton of location data on its users, and then packages it into data products & advertising products.

It wasn’t the pace of work that burnt me out there, but instead the lack of meaningful impact. Even a light workload at such a place was already heavy enough to create burnout.

Just as you need rest from volume of work, you also need rest from work that exploits others or work that does not appear to have a constructive purpose.

As I've gotten older I've found that what type of work I'm doing matters less and less. It can be the most interesting project in the world, but if your teammates are all assholes you'll be miserable. Meanwhile, the cleaning crew has a solid working relationship with each other and are having a great time.

You probably shouldn't make your "meaning in life" reside completely in your work. But then again, you can't work at a job that is completely meaningless to you.

The problem with burnout generally comes from the feeling of pointlessness. And IT excels at that feeling. We've built an industry that is accustomed -almost to the point of being a fraud to society- to such things as:

- Extremely low productivity in the large. While workers may be fully occupied, and even over-worked sometimes, in the large, a lot of productivity is simply wasted in projects which never take off, are discarded, scratched, changed, etc.

- Low accountability. Current trends like #NoEstimates #NoTesting #NoProductOwners etc, while may or may not have valid points all lead to a larger #NoAccountability "ideal" where developers seem to want no accountability at all for whatever they do. Not having any responsibilities in what you do is actually not the good idea some think it is.

- The pervasive idea that it's all horrible but that's alright. That you don't really need to know how to do stuff, you can just copy-paste it from SO or whatever you find on Google. That programmers just don't know what they are doing but haha I change this line here and it works and I don't know why but it works and that's what matters so I'm going to sarcastically twit about it because everyone will understand and concur. That everything could just crash and burn in microseconds but that won't really happen, right?

- The masterful move of claiming that anyone can program with just good will and disposition. That a degree doesn't matter, that experience doesn't matter, that actual knowledge is secondary to "passion".

All this ends up producing the result that a lot -most? probably so- of jobs in the industry and a large part of every job in the industry is mostly pointless, or at least feels so. And this pointlessness in turn is what produces the burnout.

And I don't really know, but I would tend to think that no matter how much meaning you find outside your job, if that job doesn't at least give you a minimum meaning, you will have a very hard time fighting burnout.

A lot of the "No Accountability" stuff to me started to appear about the same time as Agile. Agile removed most of management's accountability and product management's accountability. They could do whatever they want, engineering can just pivot on a dime when they're wrong. If PM asked you to build something ridiculous it's waved away through Agile, it was always too hard to figure out what to build before you build it, so PM can do no wrong.

I think some of the "No accountability" trends on the developer side are just a response.

But all of it makes the workplace a lot harder to stomach.

You absolutely can, and millions of people do every day.

When speed became a major factor in this new startup dominated tech world, people think that they just don't have time to plan.

> Low accountability. Current trends like #NoEstimates #NoTesting #NoProductOwners etc, while may or may not have valid points all lead to a larger #NoAccountability "ideal" where developers seem to want no accountability at all for whatever they do. Not having any responsibilities in what you do is actually not the good idea some think it is.

When developers are not given time to plan and test, what does one expect?

That programmers put in their spare time for the company? Ha!

> - The pervasive idea that it's all horrible but that's alright. That you don't really need to know how to do stuff, you can just copy-paste it from SO or whatever you find on Google. That programmers just don't know what they are doing but haha I change this line here and it works and I don't know why but it works and that's what matters so I'm going to sarcastically twit about it because everyone will understand and concur. That everything could just crash and burn in microseconds but that won't really happen, right?

Again, if developers are not given time to reflect like post-mortems and such, what do you expect?

> - The masterful move of claiming that anyone can program with just good will and disposition. That a degree doesn't matter, that experience doesn't matter, that actual knowledge is secondary to "passion".

I used to believe that passion is important. But after a few years in the field, more often than not, it is used as an exploitation vector.

For me, happiness requires a meaningful life. If I tried to get rid of that dependency, I'd probably end up a broken man and try one of the above ideas.

Since leaving tech my life has also become more balanced in other areas of life such as relationships and physical health, which I didn't mention in the article. Thanks for pointing that out!

And the flipside of separating things like that, is that when activities you enjoy are freed completely from having to be a source of money, they sometimes can start to be more fun and meaningful in their own right.

Plenty of people will get all their meaning from work, and they’ll burn out trying to prove who they are.

Plenty of people hate being defined by their work and want to be recognised for their self.

Funny, someone at work just shared this article: https://www.theatlantic.com/amp/article/583441/

If you set your priorties you will usually get your most desired outcome.