Computing

How to not get burnt out coding at work and at home

Submitted by 43423432423, , Thread ID: 129451

Thread Closed
43423432423
Newbie
Level:
0
Reputation:
0
Posts:
15
Likes:
0
Credits:
16
28-04-2019, 12:51 AM
#1
Hey, being a programmer and working a normal 9 to 5 job.
I always want to do some hobby side projects at home, but after coding all week at work I just feel too tired of coding.
Even if I would love to create some things I envisioned, I just can't force myself to code some more.

I tried watching some shows while coding but that was just too distracting and I lost all productivity.
What helped you guys with avoiding "coding burnout"?

RE: How to not get burnt out coding at work and at home

Starboy
Member
Prime
Level:
0
Reputation:
28
Posts:
146
Likes:
31
Credits:
127
28-04-2019, 01:39 AM
#2
28-04-2019, 12:51 AM
43423432423 Wrote:
Hey, being a programmer and working a normal 9 to 5 job.
I always want to do some hobby side projects at home, but after coding all week at work I just feel too tired of coding.
Even if I would love to create some things I envisioned, I just can't force myself to code some more.

I tried watching some shows while coding but that was just too distracting and I lost all productivity.
What helped you guys with avoiding "coding burnout"?

I understand after working you are tired. Normally whenever Im tired but I still want to do something I listen to music, normally very upbeat like rap or R&B. Comedy is also always fun to listen to, I hoped this helped.

RE: How to not get burnt out coding at work and at home

aeronex
Novice
Level:
0
Reputation:
0
Posts:
34
Likes:
3
Credits:
41
28-04-2019, 05:40 PM
#3
I used to work 14 hours daily on coding, burnt out in 5 months after just 1 project. The key I learnt is to either have good project management skills or have a good project manager. A good project manager is a good risk calculator and calls out bullshit against the customer for what's not reasonably possible. If you have a good team of developers, you don't want them contributing to team attrition rates because they get burnt out. And then you always set buffers. Something that takes 2 months should be planned for 2.5 months - simply because people tend to give best-scenario estimates.

Users browsing this thread: 1 Guest(s)