Live data from Hacker News

How to Burn Out Programming

blog.braegger.pw

21–30 of 119 posts

Re: How to Burn Out Programming

#21

Now how about an article on how to recover from burn out, doing nothing all day for a couple months doesn't seem to be working out.

Strenuous exercise under conditions of intellectual engagement works wonders. Try rock climbing, whitewater kayaking, or any other strenuous activity with enough danger associated to keep you focused.

Re: How to Burn Out Programming

#22

My list would be more like -- How to Burn Out Programming: 1) Do it too much for too long while being under stress. The same way you burn out doing anything. 2) See #1 I do agree with some of the points laid out in the post, but disagree with #2 and #4. #2 ("Have a negative attitude toward everything") is a bad thing for team morale and should be avoided but I don't believe it has anything to do with burnout. #4 ("Sw…

The problem with #2 is that the author lists it as something that causes burnout when instead is one of the likely results.

I agree about #4 and many of the things he lists are a bit subjective and for some could be again result of being burnout. Your career stagnates even if you persist remaining in the same useless place forever and sometime starting anew somewhere else, on new problems, could at least temporarily help someone suffering from burnout.

Re: How to Burn Out Programming

#24
post #4
post #3

[deleted]

I've never been burnt out(yet). What does it feel like?

The most relatable way I've found to describe it as that after burning out it takes 100% of your current effort to achieve 10% of your previous output.

That's ignoring the random bouts of crying for no particular reason and things like that, because I'm pretty sure they're unique to each individual.

Re: How to Burn Out Programming

#25

My list would be more like -- How to Burn Out Programming: 1) Do it too much for too long while being under stress. The same way you burn out doing anything. 2) See #1 I do agree with some of the points laid out in the post, but disagree with #2 and #4. #2 ("Have a negative attitude toward everything") is a bad thing for team morale and should be avoided but I don't believe it has anything to do with burnout. #4 ("Sw…

    I've had to quit a couple of jobs due to the fact that 
    staying there maintaining the same old code base ... 
    would have been what resulted in my burnout.
Agreed––though if this is a problem for you, try consulting. But it's easy to forget that boredom can cause burnout too.

Re: How to Burn Out Programming

#26
post #8
post #4

Earlier quoted context omitted.

I've never been burnt out(yet). What does it feel like?

Well its a form of depression. If you'r feeling unmotivated for longer periods time, frustrated at all the stuff you still need to do but still can't start, often procrastinating for days/weeks before you can make small progress.. Then you are probably burnt out. A project with big ambitions, tight deadlines and a small team and budget will get you there some time.

You are so right. It's even more accurate then the OP shows. We've all been there. But the thing is how to get out of it. A project with big ambitions and tight budget can not be stopped, but has to be delayed while you are recharging yourself.

One thing I always avoid is depriving of enough sleep which will cause physically burned out and it's hard to recover as other people mentioned. It may cause long term negative effect. If it happens in a short term, make it up quickly to fully recover yourself and come back to the energy level soon.

Psychologically if we are burned out for a certain task, we can switch to some other type of tasks instead of doing nothing productive. But sometimes, it's hard to keep the engine running without burning out of fuel. For most of the startup teams, after reaching a certain milestone, it will be followed by a lot of lip service or brain storming before they gear up towards a new target.

Re: How to Burn Out Programming

#27
post #24
post #4

Earlier quoted context omitted.

I've never been burnt out(yet). What does it feel like?

The most relatable way I've found to describe it as that after burning out it takes 100% of your current effort to achieve 10% of your previous output. That's ignoring the random bouts of crying for no particular reason and things like that, because I'm pretty sure they're unique to each individual.

Seconded. What I notice most when I'm on the verge of burnout is a lack of capacity for stress. Say when something breaks first thing in the morning - under normal circumstances, it's cause for some grumbling and maybe frustration at the time taken out of your day. When burnout is at hand, I'm just out of my mind. I don't have the tolerance for even the minor stressors, and nowhere close to my normal patience for the slow, thoughtful work necessary for top performance.

Burn out - for me - means a shorter temper and less productivity.

Re: How to Burn Out Programming

#28
> "4. Switch jobs often"

This is true, but the other extreme is also true - being too loyal, stuck in a soul sucking boring job dominated by internal fights and politics, can also lead to burnout. Sometimes it gets tough to find work you enjoy doing.

> "5. Work long hours, ignore your life"

This should be the number one reason for burnout. I think it happens most often with young developers in their twenties that don't have a family to get back to at the end of the day. Personally I now have a wife and a 3 year old son and I'm always happy to return home at the end of the day or to engage in various activities over the weekend. And because I do that, I enjoy most Mondays.

Of course, we are software developers, we like what we do, many times we want to work outside regular hours. But personally I have a general rule that I always apply -> I never work overtime or on weekends, unless I'm in the mood for it or if there's an extreme emergency. Therefore, I never cared when some manager or client told me that the deadline is probably going to be late, so maybe we should pull longer hours. When asked, I always say "No, sorry". My overtime is for things that bring me pleasure - implementing a cool feature that I wanted, or learning something new, or implementing something reusable and pushing it on GitHub ... you know, works of love.

There's a tremendous difference between working overtime because you're in the mood for it versus because you have to.

Also missing from the list:

> "6. Be dishonest, never ask for help

I've decided some time ago that I should always be honest with my colleagues, managers or clients. In my language we've got an expression that more or less means wasting time - "rubbing the mint". Sometimes I rub the mint - and in scrums and daily meetings, I now feel no shame in admitting that the other day I did basically nothing. I also recognize when I'm having problems, like when I'm not understanding a concept well enough or when I can't find the root cause of a problem and do ask for help ... though, because of the ego-tripping or other reasons, this is something that's often difficult to do.

It does help being honest and nobody is bothered when you admit that you were lazy the other day or that you're having problems, because everybody have the same issues in their job, even if they don't admit it.

Being honest and recognizing your own flaws helps with not feeling guilty. If you're lying to your peers that you got work done, that you're close to solving the problem, etc... that's accumulating debt that you have to pay in the days that follow and it can lead to a snowball effect.

Re: How to Burn Out Programming

#29

Now how about an article on how to recover from burn out, doing nothing all day for a couple months doesn't seem to be working out.

Ouch. My theory is that it's related to ego depletion. [1] If that's correct, you should find things that you want to do, and do them. Start small. And do your best to not focus on the burnout; focus on what you can enjoy about what you are doing. Look for little victories; I'm convinced that accomplishing things, anything , can help recharge you. I also think social connections can recharge you. Not the kind on Face…

It's just the contrast between the person I was not too long ago and the person I am now makes it hard to believe that they're the same person.

When I think of the kid who used to tinker around with computers and electronics, I always see him as another person. There's no way that guy would ever find learning a new programming language boring, or find it difficult to get out of bed for classes he was really excited about.

I appreciate the post and will try some of the stuff you suggested out. Glad to hear you had your first really good day! This isn't the first time I've felt stuck in a rut and I know how great it is to feel that way. :)

Post reply on HN