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.
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.