Welcome to Code Chatter, your go-to series for conversational coding insights. What makes this series of questions different from all the others? Well, truth be told, not much, but they're still thought-provoking and fun. Join us as we explore the coding world, one witty question at a time.
Could you share the story of what led to your first experience of burnout from programming?
Follow the DEVteam for more discussions and online camaraderie!
Top comments (4)
It’s happened to me so many times over the last few years
I’ve made it a point to not burn out while building findcool.tools
I’ve realized what usually leads to burnout for me:
Now I make sure I workout a few times a week, sleep 7-8 hours, eat well, and make sure I recognize the signs of burnout.
This has allowed me to avoid it for the last few months.
The majority of programmers work in the night.
My first burnout from programming was 3rd year college:
I was the technical contact for two groups of students (including my own) on a project I'd been working for the summer prior with our only contact at the project that was absolutely not technical (this is not necessarily a bad thing, just a relevant detail).. and no one aside from me had used the stack the project was built on before so I was the first person anyone asked questions to and was teaching everyone enough about the stack so they could work with it. I basically spent the rest of that year and about half of my fourth year burnt out and trying to write as little code as i could to get by. Was very glad when my 4th year capstone team let me happily plug away at some infrastructure stuff instead of writing a lot of the heavier code for our project.
I read a lot of documentation, tutorial, books (database, algorithms, software engineer), learn a new language, read code of other developers and solve some problems.
I AM OVERBURDENED!