I'm in a lucky position where "getting burnt out" comes hand-and-hand with "being super engaged at work." Weeks can go by where I'm watching the clock, but then something holds my attention for longer than a few hours and all of a sudden it's 3am and I'm still diving deeper and I've got a meeting at 9am and my partner fell asleep waiting for me to come to bed. 😄
Honestly, because in my experience getting burnt out follows days of supreme mental engagement, frustration, and ultimately growth, I look forward to the next time. But I haven't experienced a "death march" yet, where I was forced / strongly asked to work more than I wanted, so I'm still pretty naïve.
And as a bonus, my company and colleagues don't expect you to work yourself hard enough to get to that point, and they always appreciate it when you do: hard work is not taken for granted at Tapjoy.
I'm also rather masochistic (but not in a general way, not a sexual one): when I notice myself getting burnt out, I push myself harder. I relish the feeling of discovering my limits and challenging myself to ignore them until they expand.
Probably not the healthiest behavior, honestly, but I am who I am 🤷 and I'd much rather be fatigued from pushing myself, than lethargic from not.
It's pretty selfish of me to behave this way, though: I do a disservice to my teammates by not taking care of myself. Giving my best doesn't mean giving my all, but I have trouble remembering that.
Principal software engineer at a fintech company, leading designs and architectures. Sharing personal insights on technology trends and their impact. My posts are based on my personal opinions.
Location
Chicago, IL, USA
Education
Bachelor's in Information Technology (Mackenzie) and Master in Financial Engineering (WorldQuant)
Work
Principal Platform Software Engineer at Enova International
Every quarter end. Normally the rush to finish projects and the excess workload of planing the next quarter is what kills me.
To handle it I try to delegate more and focus on tasks that have dead line.
As for me, I usually do prevent myself from getting to a point of burn out by not coding during the weekends or doing some minimal coding tasks over that period and during that time I do blog on this forum to improve my technical writing skills, So far so good
Top comments (6)
I'm in a lucky position where "getting burnt out" comes hand-and-hand with "being super engaged at work." Weeks can go by where I'm watching the clock, but then something holds my attention for longer than a few hours and all of a sudden it's 3am and I'm still diving deeper and I've got a meeting at 9am and my partner fell asleep waiting for me to come to bed. 😄
Honestly, because in my experience getting burnt out follows days of supreme mental engagement, frustration, and ultimately growth, I look forward to the next time. But I haven't experienced a "death march" yet, where I was forced / strongly asked to work more than I wanted, so I'm still pretty naïve.
And as a bonus, my company and colleagues don't expect you to work yourself hard enough to get to that point, and they always appreciate it when you do: hard work is not taken for granted at Tapjoy.
I'm also rather masochistic (but not in a general way, not a sexual one): when I notice myself getting burnt out, I push myself harder. I relish the feeling of discovering my limits and challenging myself to ignore them until they expand.
Probably not the healthiest behavior, honestly, but I am who I am 🤷 and I'd much rather be fatigued from pushing myself, than lethargic from not.
It's pretty selfish of me to behave this way, though: I do a disservice to my teammates by not taking care of myself. Giving my best doesn't mean giving my all, but I have trouble remembering that.
Every quarter end. Normally the rush to finish projects and the excess workload of planing the next quarter is what kills me.
To handle it I try to delegate more and focus on tasks that have dead line.
As for me, I usually do prevent myself from getting to a point of burn out by not coding during the weekends or doing some minimal coding tasks over that period and during that time I do blog on this forum to improve my technical writing skills, So far so good
Great tipp