I hear senior developers saying I shouldn't do it because I will get burned out, I hear not so experienced ones saying we should use every moment we have to write another line of code. Some even look down on you and think you're not passionate/ serious enough about your job, just because you don't breath code 24/7.
While I do do work related things after clocking out (and I'm not opposed to that, since I don't have a great deal of experience and there are many things to learn), I can't help thinking about that people working in other fields are not really expected to take their work home with them - I don't see my friend who's a nurse going around and giving shots to her neighbors, after her working hours are done.
What's you opinion on this? Is the amount of time spent coding outside office hours an indicator of how good/ passionate of a developer you are?
Photo soource: Kevin Ku on Pexels
Oldest comments (87)
You will get burned out, for sure (i got burned after 1 year of non-stop coding). I usually code after my working hours only when i find something new/interesting to play with. If it's just a routine work, i won't do it in my free time.
Yeah, that's something to watch out for.
What I like about coding in my free time (when I'm able to) is that there's no pressure. So even if I don't have the time to, I don't have to worry about it.
I'm still not there. Sometimes I feel bad that I don't use my free time for more coding. Most of the days it's like this but I have periods when I can relax and not care about it.
Same here. Usually when I code in my free time is to try something new.
I think it depends on each individual person. Some enjoy coding in their free time, some like to only code during work hours, and some are in between. I don’t think any of these options make one person a better developer than another. It’s all about balance for each individual.
I personally love writing code as my day job and enjoy writing code outside of work from time to time, but I also have a lot of other interests that I like to spend my free time on. I may spend more time coding outside of work if there’s a specific project I’m working on, but I also like to devote time to non-coding projects and activities that interest me.
Yes, different strokes for different people. I want to add to this that it also isn't black and white. There are times in my life where I totally do code in my free time, but this is not always the case. Sometimes I do nothing, watch movies, play video games. Other times I buy am ukulele and just practice that for a year (yeah, very specific :) and if I'm feeling it, I will start writing code again, because, this is the most important part I want to and enjoy it.
Then there are those of us who only code in our spare time, but have been doing it almost daily for well over the past 20 years 😁 I adore it and can't get burnt out, but it might not be the same for you. Then again, you never know, it might😁
You mean coding is your hobby and not your day job? If that's the case, then yes, you're a different category :).
what stacks are you into?
I can write in various languages, high and low level; though since high lvl languages have always served my needs I tend be more comfortable with interpreted/scripting languages. I started writing all the basics 20+ yrs ago - Batch/CMD/PS then started C++/Assembly. I occasionally write small cli or simple math bins in those, but everything I've' needed done in the last 10+ years was easily done in AutoHotkey/Python in Windows and Shell (Bash)/Python in Linux. I can also write HTML, CSS, PHP, and very familiar with vanilla Javascript as I have used them for many years to build personal sites and UserStyle/forum themes. I've read lots of introduction books to many other languages and familiar enough with their syntax. I am more than familiar with many different programming constructs and I read any programming/computer science book I can get my hands on. I don't have a professional stack, but I guess that's what you'd call mine.
I think isn't mandatory but recommendable in some situations, specially when you are a junior. Also is a good idea to code in your free time if you want to try different things, like you're only doing backend in your work and want try frontend or mobile.
Yes, that's what I'm doing at the moment, just because the office hours are not enough to get up to date with everything I need to know. I usually use the weekend for that since during the week I'm already too tired (juniors get tired faster :D).
No. Find a way to live a well rounded life. I love code, and have done for 30 years, but there is more to life. If you're doing it out of some sense that you have to keep up or catch up - here's a secret - YOU NEVER WILL! Not because you're a bad programmer or bad human, but because it's impossible. You will be a better programmer in the long run if you allow your brain time off to recharge.
Crunch time happens occasionally (1-2 times a year is enough). Try to be balanced the rest of the time. If you are finding that hard, have a think about why - internal or external factors.
This might be relevant.
codingmindfully.com/the-software-d...
I always have the feeling I will never catch up or I won't know as much as I need to know but I suppose this is a feeling everyone is struggling with. Thank you for the resource, I was pleased to find out that I'm not experiencing any of the symptoms of a burnout developer :).
Glad to hear! It's completely a feeling everyone struggles with. There is too much software engineering to fit in a single human mind! So enjoy the process of learning and admire and take inspiration from those who know a lot already!
Also - if it's a case of other people looking down on you - that's often a self defence mechanism that hides their own lack of self-worth. They set themselves up as superior by diminishing everyone else. It's not sustainable for them, and isn't true about you. So brush it off.
Then there's the question of are people actually looking down on you?
Imposter syndrome's a bitch. It likes to make us think others think less of us because we don't know everything about everything, and yet we all have that same insecurity. Maybe not all of the time, but we've all dealt with it. We've all felt like we're "less-than" or whatever, because we don't know something someone else does.
This field is massive and growing every day. You're not going to know everything about everything. You're not even going to know everything about your little niche. There will always be someone who knows stuff you don't.
And you know what? You also know things other people don't know.
Embrace what you know and share it. Learn the relevant stuff you don't know but need to know. Outsource the rest. Fill your niche, let others fill theirs.
No, you shouldn't. Only robots are work without any interruption. Your self-improvement is also important. People shouldn't be a lover of their job. This should be a hobby. When you write code all the time, you may get burnout syndrome.
In the past, I met a lot of people who had burnout syndrome. You should do different things o remember you're a human. Read books, do gym, cook something, draw something or dancing, etc.
The job we love shouldn't kill us. I wanted to die about one year ago because of different reasons. This job was one of my reasons to kill myself.
My girlfriend lied to me. Because of this, I was really sad, and I was under stress while doing my job. Sometimes, I've failed because of these reasons.
Thinking more, really bad idea. This is a kind of die. Let your mind be free. You'll be more successful.
I'm sorry to hear you went through bad times, I hope you are feeling better now. And I agree, we should avoid burnout as it might even make you quit coding all together - I know someone who actually did.
Do you like to watch movies? Do it.
Nowadays, I'm trying to improve my English. I loved these words, "I know what I have to do now. I gotta keep breathing. Because tomorrow the sun will rise. Who knows what the tide could bring?"
Stay strong :)
I have child so it's impossible to code 24/7 :) But seriously, do not code all day long even if it's your great passion. You will burnout really quick and be tired of coding. Even juniors whom need to code much to learn, should have breaks (IMHO).
I do think coding for too long might give you the wrong impression about what the job means and you risk giving up or end up hating it, when it's not the case. Balance it's important and coding should be fun.
I think I should code outside of work. I find it relaxing to work on my own projects. I view it as a hobby, in which I can do what I want.
However, I don't think that anyone should code outside of work. If it doesn't feel right, turn your screen off and do something else. You've got your own pace of learning new things. It's important to recognize that, as submitting to a faster one can quickly drive you towards frustration and burnout. If you spend your time coding when you think it's right, you're being more effective in the long term.
Also, noones's writing code all the time even when in office. Concentrating for 8 hours straight is nearly impossible.
You're right. This is something that I noticed and I believe is true: whenever I'm trying to force myself to code, I tend to procrastinate and even if I'll end doing it, I won't be very productive. When I'm in the mood for coding, I lose track of time and I actually achieve things, way beyond what I planned. Thank you for your input.
It should not be an obligation, and you should get some fun from coding outside of office hours. And it should not be to work related, so not a poc for a new thing or something.
I am struggling with doing the 'right' amount. While programming in free time used to be just for fun, it's now often to prepare for talks, or contribute to open source. And that makes it a lot more like real work.
It also depends on your work. Especially when I just started I was often overwhelmed by the stuff I needed to learn to do my work, so there really wasn't any room to learn additional stuff.
Try to find the balance that works for you. Learn enough to tickle your brain, not su much to burn it out. And the correct balance is very personal and depends a lot on your private life as well.
It also depends on your work. Especially when I just started I was often overwhelmed by the stuff I needed to learn to do my work, so there really wasn't any room to learn additional stuff.
This is where I think I'm making some mistakes as I am already overwhelmed at work and I come home and try to push it further. My more experienced colleagues told me to take it easy so now I keep these learning sessions mainly for the weekends.
Thank you for your input.