While there's a romantic vision of the starving artist, being broke is a whole different type of burnout.
Even if you're creating fine art exclusively it's possible to make a good living at it if your art has mass appeal.
The problem is when you make art that's not really geared towards the masses. If you make something widely considered "ugly" or disturbing, that most people wouldn't want to hang in their living room or on the walls of their business then you've got a problem.
The other problem is if you've either got a style that looks too much like everyone else or if you don't have a consistent style. Then people can't distinguish your work as uniquely yours and that makes having a "brand" difficult to impossible. You can still get by this way (especially if your work still has mass appeal -- see the endless impressionist-style paintings out there), but it's still a lot tougher than if you have a distinctive style.
The most successful fine artists have both a distinctive style and mass appeal... or a good marketing team. Often marketing is actually more important than the art itself as far as sales go.
Problem is many artists aren't good at marketing and just want to make art and aren't yet famous/rich enough to afford to hire someone to do the marketing for them.
Well, apparently there’s also a lot of money to be made doing very specific commissions.
Not quite sure where I heard about that, but the concept of ‘whales’ exists there as well.
I think most burnout is systematic, and caused by incomplete task breakdowns.
I also don’t know if full eight hour days are good, in general. I feel like 5x6 or 4x8 would be a better schedule, though, with a four day week, I’d be curious to try “weekend Wednesday” out instead of just having a three day weekend.
I do wish I could do the same number of hours over 4 days instead of 5, though.
https://en.wikipedia.org/wiki/Piece_work
And it's already really common for non-employee contract work to function that way. The guy who mows my lawn gets paid the same amount no matter what speed he mows it.
That being said, there are plenty of salaried jobs where people are assigned measurable responsibilities to attend to and don't have assigned work hours.
As a counterpoint, I think burnout can contributed to by overly granular task breakdowns that remove individual developer creativity and autonomy.
One day on the computer when I was fighting with a stupid custom-made build system, I muttered to myself, “anyone who says a good carpenter doesn’t blame their tools never had to use an exploding hammer.”
But anyway most "fixes" are really just changing systems to adapt to change in other systems. I spent 3+ years at Google just migrating this and that and the other subsystem to a different datastore, and knew dozens if not hundreds of developers stuck on a treadmill of constantly rewriting to adapt to other people's rewrites.
It's that your work load seems to only increase. As the study found with regards to the causes of burnout, increased workload cited as the main reason.
I'm still providing updates to stuff from over five years ago (that has officially been retired), while my boss is breathing down my neck about new projects. The stress of doing this, the stress of trying to manage my manager's expectation, the stress of realizing you'll never be able to really put any of your work out of your mind or have a lighter load of responsibilities, etc. is what leads to burnout.
Dev shops don't have to operate like that, and all it takes is one person to have the fortitude to say no.
It's also a bit thankless, being good as this job, in a lot of cases, means you are moving really fast from one task to the next without any down time in between. I find it hard to get to a place where I can feel accomplished or proud of a piece of work, because the next fire/high-priority task is already "behind schedule".
I think part of it may also be due to the fact that the job is constant problem solving. Even though its nice to find solutions to problems, knowing you'll be perpetually in a state of "there is a problem that must be fixed" is taxing on mental health (for me at least).
Something I've seen more and more often is that a lot of developers take a lot of time for every ticket. Much more time than I'd take, but I suppose it's because they are not incentivized to work fast, they'll still get paid the same no matter how many tickets they close. But I don't think paying more if you close more tickets is the solution, I don't have any solution, really.
Some common ways that happens in software development are working for months on a feature that gets cut (or undercut) at the last minute, or trying to demonstrate your ability for some role and not being recognized for it, or even just putting your heart and soul into a company that is circling the drain.
If those experiences happen over and over, without some intervening successes to recharge you, you get burned out.
Apparently some AWS tools also got changes since some scripts seem to be failing.
It is so stupid to host anything in the cloud if you don't serve millions of users... Not really burnout, but I hate it so much right now...
Maybe it's agency? Ultimately I don't feel like my contribution wows anyone.
So maybe the trick is evangelizing? I really don't know, I just know I've been successful, often in spite of the organization I was in. I'm also constantly aware of the amount of luck involved in everything I do, so it's always hard for me to believe that I was the important factor.
There's something deeply satisfying to me in cutting out thousands of lines of code and no-one even noticing.
I will even go back and look at that commit over the next few weeks with a feeling of peace and accomplishment.
I've sometimes 'stolen' time from feature work to do that refactoring, and it's the massive reduction of complexity and TLOC that often gives me satisfaction, not delivering the feature.
Don't get me wrong, I've delivered features and applications I'm proud and happy with too, but I think there's a significant minority of us who really enjoy deleting tons of bad code too.
Eg there's a common saying, something like "Don't let your passion become work". Implying that if you love creating art, it can be a struggle to keep that same love when you start creating for other people. Of course it's all variable, but i hope my explanation suffices.
Programming can often be similar in my mind. Sometimes i can be in the height of feeling super uninterested in my work - tired, exhausted, all things i'd collectively describe as progressing towards burnout... but then i daydream and get the urge to go code some random idea. The fire is still there, in me, to be creative and produce something in the way i enjoy. It didn't seem inhibited by my work at all. It just seems work is following down a path of unfun that accumulates.
It feels similar to side projects. Devs often joke about how easy it is to start something but how difficult it is to finish. Because larger projects will often become work themselves. But in this side projects you have the luxury of stopping. I suspect if you forced your way through, never stopping on them - you'd burnout in a similar way to real work. If this is at all accurate, the consistent push on uninteresting work is the driving force for burnout in these examples. You're used to doing the work with passion, but extended periods of non-passion feels a lot like burnout, to me at least.
This doesn't invalidate the conclusion, strictly speaking, but the basis for it is flawed in my opinion.
Take microservices for example. Classic cargo culting development of what Google and Facebook are doing, but usually without a dedicated staffing team of hundreds. No wonder devs are burning out if they have to learn how to run a k8s cluster where a simple binary would've sufficed.