Programmers who only code at work

pungiish profile image Jan Updated on ・2 min read

What's your opinion on programmers who are not passionate about programming, have no side projects and only program at their jobs. Not senior devs either, just programmmers, who are not juniors anymore. Can they ever improve, write better code? Or do they stagnate.
Asking because my coworker said he doesn't enjoy programming at home.

Update, 2 years later. So, I appreciate all of your responses and since I started developing full time ( not a student anymore ), I can see how people don't have much time to polish their skills outside of their work. However, I want to become better, so I rather sleep less, and try to learn about framework specific things I do not understand in detail yet. Sometimes i even work on work projects in my free time, because i like how they were developed and i want to ingrain those practices into my mind, so when I'll have to make a project from scratch, I'll predict what pitfalls to avoid and how the data should be organised. I really want to show my manager and my mentor that I am capable of not just being a code monkey, but also coming up with inventive solutions to unique problems i'll face along the way.
Now, I understand that my eagerness to work in my free time will slowly fade, but, lately I don't even feel the desire to party because I'm tired/ have work tomorrow and to be honest, I don't even miss going out. Of course, I go out for the occassional coffee, date, hangout, but sometimes i'd rather just stay at home and code 😅

Posted on by:

pungiish profile



I am a CompSci student and working as an angular/nodejs developer. My hobbies are Judo and fiddling with javascript.


Editor guide

This is a really interesting question. I guess it helps to reframe it by applying the question to other jobs.

What's your opinion on carpenters who don't build houses in their free time?

I've met a broad variety of developers in my time, and a large portion of them have been the type who have a skill that they use for work, and don't care to indulge in outside of business hours. Instead they use their free time to build boats, go surfing, paint, write, cook, raise families etc.

Some are tech leads, some are CTO's, some are juniors, the remainder are everywhere in between. Some of the best technical minds I've worked with have been superb at completely separating their work and home lives.

I noticed quite early in my career that there's an (in my opinion) undue amount of pressure on developers to be coding/reading/meetup-ing 24/7 lest they fall behind. The truth, as I've grown to understand it, is that 40 hours a week of writing software is plenty to facilitate growth and improvement, given an environment that supports that growth.

I've been lucky enough to work for organisations who take their employees growth very seriously, and as such provide ample opportunity (at work) to dabble in new technologies, learn and grow.

The idea that the only way you can avoid stagnation as a developer is to let your job consume your life* is pervasive, but very poisonous none-the-less.

Having said that, no-one's trying to stifle anyones passion here. If you love to code, do it at every opportunity you get. But be careful when passing judgement on the skill, growth and development of folks who don't share that same level of passion.

*maybe not your whole life, but a significant portion of it


Wow, what a GREAT response. I've struggled with this thinking to myself "I love to program at work -- but I am so TIRED when I get home, being a single dad, wanting to just unwind doing other stuff" and I've felt really guilty about thinking that way. You have just validated my home life with your post, though! Every developer's home situation is different. And I am also fortunate to work for a company (read: Boss) that fosters learning new technologies and improving skills. Thanks for packaging your reply in a fashion that echoes and validates my thoughts. I hope this helps other developers in similar situations!


This issue always haunts me, I'm constantly afraid of falling behind if I don't code outside of my work hours. The response you just gave is a great deal of help for people in my position. Thank you! 💖


Well said. I just wish more companies understood the need for personal growth.

I've worked with programmers who seem very passionate about programming, at least they spend all day and most nights coding, and do little to actually grow personally. In that case I'll take a dispassionate programmer who cares about improving his skills at work any day.


So it's a bad trait that I am passionate about my career and indulge in programming whenever I can? I even help moderate programming groups on facebook and mentor other younger people.. You can be both a passionate programmer and have a life. It is possible.

My original answer should be seen in the context of the original question. I was trying to find a more nuanced way of saying that I'd rather work with a good dispassionate programmer than a bad passionate one, not that all passionate programmers are bad. All I meant was that programmers with other interests may be able to bring something else to the table.

That also depends on what you mean by "have a life". Does your life include being married and having several children you are raising? Do you have any other activities that require an investment of time ( such as martial arts, dancing, writing music etc)? Are you part of a church (or other religious group) and invest time there? Do you volunteer in your local town or city to help clean greenways, rivers or feed homeless people? Do you do all the aforementioned things?
Or do you do primarily what you have listed? None of that is meant to be a criticism of you in any way btw. Just saying the term "have a life" can be amazingly broad. And the person you replied to seemed to be saying they would rather work with someone who invests in themselves outside of developing a work related skill set but is pleasurable to be around vs working with somebody who is a great coder, constantly works towards furthering said skillset but is a jerk to people.
The person NEVER said those things are mutually exclusive and it had to be one way or the other.


Just because most carpenters don't build "houses" in their spare time doesn't mean a lot of them probably don't indulge in the odd making of a birdhouse, or a canoe or something. A house is a huge undertaking. That would be like a programmer trying to create Linux in his spare time. Most don't. That being said, a lot do partake in programming outside of work (a lot of the devs I know). I think this stems from the fact most people who program (who I know anyways) do it because they love it, and are passionate about it. When you love doing something, it's not considered work. When I sit down and and start writing code, it puts me in a sort of altered state, where I am free to think and be my self. I love it. I do no consider it work at all, and is the reason I chose it as a career. Cheers!


That's a very good point. Houses and bird houses are very different things.

I think the flavour of the point I'm trying to make with this comment is that it's not necessary to program outside of work to be a great, passionate and successful developer.

No-one is suggesting that it's bad if you love to code and love to do it in your free time - I'm actually saying that's great! The issue is that I see a lot of young developers being scolded for not being "passionate" enough, because they'd rather go rock climbing than build a side project in their spare time.

I love that you love to code! There's nothing more inspiring than a person who gets true joy from their work 😊


Couldn't say it any better. Well said!


I agree completely. The danger of coding in almost all of your time that isn't spent sleeping is that you become very one-dimensional in your life (and especially coding). It's amazing the number of people that don't realize the the key to interesting ideas and "out of the box" solutions is to ensure that you're interested in many things. Sometimes the most stupid idea from another field morphs into the most amazing solution in another field.
I see many young developers falling into this trap and all of their solutions to problems are always derivative of everything they have done in the past. The truely awesome ideas are rarely directly derivative of past work, they are usually applying an "outside" spin on something that will seem obvious afterwards.
Think of the people that invented Dependency Injection. Prior to that all solutions sucked (in hindsight now of course).


Well said. I'm one of them. Life and work must be balanced somehow. In my free time I enjoy trekking, reading and do things with my adorable soul mate. Nevertheless I'm a good developer and dev lead of an enthusiastic team of skilled developers


Well said sir! I think it's great to try to code outside of work and I try to do so myself. I also value my life outside the world of software development. I find coding (and learning about coding and new stuff) in my spare time tricky, especially with other hobbies, family and a social life, which most of us do have.

Compare to carpentry, I would guess that software development evolves much faster, and if you want to progress in your career and stand out, I think doing something outside of work helps. An example would be if you are using Knockout and want to get into React, then doing a side project in React should help you in securing your next move.

Maybe this might be less important to you if your work gives you good learning opportunities (e.g personal development time, personal budget, training, mentoring, etc..), you are comfortable where you are and have great job security, you are very talented, or work in a very specialised area where changes do not happen as often, and you are happy to stay in that job.


Thank you! As somebody who only codes at work I usually I feel alienated because tech culture somehow implies I should be coding 24/7, I like doing other stuff!


Great response Leighton. I am fully agree with you.


What's your opinion on carpenters who don't build houses in their free time?

Let's slightly re-frame this question (pardon the pun):

What's your opinion of architects or home-builders who live in apartments or homes that someone else designed or built, versus those who did their own?

Perhaps some or most would have very good reasons not to. But doesn't it just say more when someone lives their discipline? That's pretty exceptional, isn't it?

As programmers, we are knowledge workers in an information economy. No one else is going to learn for us. If we're not satisfied with our level of learning on the job, no one else is going to make us learn more. So then we have to do what we can when we're not at work to get the learning we think we're missing out on.

So when we see people doing side-projects and learning on their own time, they are signaling that they are improving at their work. It's a signal that we should look a little more closely at them and consider them for more responsibility and promotions, and when we have to let someone go, they may have a leg up over their competition, all else being equal.

It's your life. You can totally choose to do whatever you want in your free time - gaming, sports, partying, anything else, or nothing at all - and if you're already a programmer, you can probably continue without any relevant stuff outside of work. But if you want to rise to the top of your field, it gets competitive, and that's where you have to do more to differentiate yourself.


Yeah, great reply.

Separate work and home lives well is essential to make more creative works.


Very well articulated! Totally agree.


In France people can't be fired easily so they don't feel pressure to do coding out of work :)


Really great way to put it. Kudos to all the companies who care about their employee's growth😃


I would be careful about assuming they're not passionate because they don't code in their free time. At one point I was a single mom and couldn't find time to code unless I was at work. That didn't mean I wasn't learning new things while I was at work, or that I wasn't interested in technology. :)

Passion to learn and strive to be better is what sets people apart from becoming stagnate.


That's absolutely right, coding only at job and barely on the free time doesn't mean somebody is not passionate, but it can mean there are other people, friends, family, kids who need you and you have to dedicate to them your time. Agree totally that what you do at work can give the same results in developing your skills than coding at work and after work, but that's really depend on the job


I often code significantly outside of work (several hours a week). And there are a few things I want to say about that:

  • I really enjoy coding. If I didn't enjoy it, I wouldn't do it on my own time, and I might not even do it as a career.
  • I learn a lot more from my side projects than I do on the job. The nature of a side project demands it: everything is up to you. You have to learn how to do everything from beginning to end, because (unless you're very lucky) no one else is going to do it for you.
  • My excitement about side projects ebbs and flows. Sometimes I'll go a couple of months without doing any coding outside of work. I would hate it if coding outside of work became a requirement or expectation at any job.
  • I have definitely been given advantage over other candidates in the job application process because I'm able to talk an interviewer's ear off about the side projects I'm working on and how awesome they are.
  • I don't have a CS degree, so I often feel like I have something to prove. My GitHub graveyard is one of the ways I demonstrate that I can kick it with the grads. I believe that every self-taught programmer must face the same existential challenge, although there are other ways to do it.
  • Programming experience, in my opinion, is pretty fungible. A guy that has four years of work experience plus six years of hacking around in his spare time is often comparable to someone who has 10 or so years of work experience.
  • Scientists and tradesmen (doctors, chemists, plumbers) aren't usually expected to "practice" in their spare time. Artists (actors, photographers, writers) often are. I see programming as somewhere between these two worlds. And I think either approach can be successful.

Side projects are just one way to prove that you're passionate about your work and willing to learn new things. If you'd rather surf outside of work, that's cool -- someday I hope to have a hobby as cool as that -- but you'll have to be prepared for competition from those who live, breathe, and poop code. Doesn't mean you can't win. :)


I love this attitude. I love to code as well and enjoy working on my side projects. How I keep sane is balancing my other hobbies, Specifically the nontechnical ones like music.


Great reply. I fully agree here.

Sometimes I feel ...guilty? that I love code so much that it's my main hobby.

I guess it depends on the individual, but for my personal development I feel that supplemental coding helps me stay up-to-date on the latest trends and practices and news, since I don't always get that in my job.


Great response. Since in your actual work you don't learn too much (because the nature of the projects), have you considered being a freelancer or get some revenue of your personal projects?


I don't want to commit my free time to a contract (since it's off-and-on at times) but I hope to figure out how to build things that are worth money now and then. I really believe the projects I build on my own are high-quality stuff, and it would be cool if they provided value to someone else.


This is exactly the same for me! I couldn’t have explained better than you. Thanks ;-)


The 'elitism' and the 'with us or against us' attitude in your message is why so many people who code majority of their waking hours are poor colleagues.

Software development is in itself a team oriented environment. You play with the team. In a proper, healthy work environment, you'll go as fast as your team goes.

There should not be any pressure to feel that you need to code outside of work. It's great that you're interested in a side project, but it's not mandatory. If you're not learning at work, then you're either too stubborn or think you know it all, or it's time to move onto your next job where you feel challenged.

Moreover, for all you know, that person, who is enjoying a sport (say volleyball), is learning the value of teamwork, team coordination and leadership. Important soft skills that, as recently discovered by many companies, are more important than the technical skills.

Just because you code outside of work day in day out does not mean you're better. Stop giving yourself the delusion that you are. A colleague with the learning mindset however - will always be successful as they are humble, curious, and easy to work with.


Strong words. I think you might have replied to the wrong comment? I expressed neither elitism nor "with us or against us" sentiment. In fact, I made it clear that while coding outside of work has been advantageous to me and made me a better coder, I don't think it's a requirement and I think other kinds of coders can be just as successful. I do it because I like it, not to exclude others or get ahead.


I love code, but I could envision a future where I only code at work. This weekend I did a bunch of photography, went to the farmer's market, the gym, wrote a tiny bit of code and I really could have done without. None of it had to do with whether or not I like to code.

I do code at home and like doing it, but in the future I could see putting my focus elsewhere and be pretty happy about it.


indeed we should do things in moderation if you are coding all time, you might as well stay in one place and have food tubes and water tubes, and start coding.


Two comments:

  1. Give me a competent colleage who only codes at work over an enthusiastic magpie developer, any day of the week

  2. Having brief experience with every new library and framework out there is equivalent to having 10x 1 year's experience compared to actually having 10 years' experience. The latter of those usually involves maturity and business sense, which is of far greater value.


There is an underlying assumption that you don't have time to learn at work - if that is the case then I'd urge you to aim to find places to work that do encourage learning on the job. I recently took a week off for a course paid for by the company. I learned and implemented React & Redux in the last two years as well as given back by training people on testing tools, development process and so on inside the last year, on company time. In production, at scale.

At my previous company I learned a lot about the agriculture industry, mathematical modelling, Microsoft Solver, C#, ZeroMQ, Redis, and many other things all on company time and with company resources. On real projects. That were used at scale. Far better than any side project.

I would say that the worst developers I've ever worked with did the most out-of-work coding. I've got about 20 years experience at this point and I will not budge on that point as it has been routinely true in every place I've worked. The best developers worked 9-5 and sometimes a little more and the worst seemed to work at home every single night and weekends.

Now I don't think people that work a bit outside of work a bit from time to time all suck, that has just been my observation of those that code outside of work a lot. I'm not sure there is much to learn there except that I know a lot of people think they have unlimited capacity for coding but we're all human and you really do not. The most 'ninja' coders I've ever worked with had hobbies that were well outside of coding and tended to be the people that could synthesize between many disciplines easily.

In the end how fast you type, how quickly you navigate code bases, the number of languages and frameworks you barely know and even how well you can engineer solutions, refactor and so on are not the skills that will take you far in this game. Soft skills, business analysis, team work, restraint, self knowledge and understanding your own personality are all far more valuable once you get past the first five years.

If someone told me they read well known books on coding, management, team structures, or anything business related every month I'd take them over someone that codes and extra week a month.


Yes, I totally agree with this. The people that were absolutely the hardest to work with were the ones that spent all their outside time coding. They knew code and had solutions for problems, but they never seemed to have solutions that other people wanted.

(Note: I'm a game programmer.) The overwhelming problem is that you could strongly argue that being a good developer does not mean being the best coder. In my industry, you're a much bigger asset if you understand human interfaces, or gameplay flow or any number of other things that go into making good games. I'll TEACH you how to write code if I have to, but it's so hard to make some coders understand what makes good games.

I want to work with people that live and play in the real world because that's what comes back into the games we make.


We also have a perfect example of this in that we recently pulled a marketing person into our engineering team because she'd shown a consistent interest in the technology side of things. She'd coded up some partials in our static site generator and so on.

The fact that she has the marketing knowledge AND can now code means she is kind of a double threat.

Where I went to college in Australia you couldn't do just a law degree you had to do law and something else like science, medicine, whatever as they sort of realise you need some other background knowledge to apply to legal situations. I think software engineering is intrinsically the same. There is very little you can do, that is useful to people, without an understanding of a completely different domain.


Sometimes, if I'm really gripped by a particular problem, I might hack away while at home. But most of the time, I leave work at work and do very little coding at home. After a full day of work, I need to relax. I need to balance my daily activities, or else I would get burned out on coding entirely.


There are several different things at stake here.

The first is being passionate about your job and the other is putting extra hours into it. If you program at home, it's likely you are a passionate programmer, but you can be passionate without programming outside of your job.

I'm always weary of the philosophy that define "real programmers" as people programming during their spare time because I feel like work-life balance is not valued as much as it should in our industry.

On the other hand, I found that working with programmers devoid of any passion for this activity was lackluster because they usually didn't care about things like emulation, mentoring, challenging other's choice or defending theirs. Ultimately, I think this attitude leads to stagnation and makes things worse for the whole team.

But it has nothing to do with side projects or the lack thereof. I've met a lot of great programmers that didn't code outside of work hours. Attitude in the work place is what matters most.


My opinion is that it sounds like you and your company feel they have a right to an employee's non-work time, expect learning to happen outside of work hours, and are trying to extract as much as you can, and expect everyone to perform at this level.

People with supportive workplaces, given adequate time to train themselves, don't stagnate. People pressed to produce as much as they can without learning new skills then use their spare time to learn burn out or stagnate.

Some of the best programmers I have worked with don't do it for fun. Some of us have other things we prefer to do: write, cook, paint, draw, build communities. All of those things also feed into us being better programmers, and it's deeply short-sighted to think of folks who don't code "at home" as lesser.

On top of that, this works out to be sexist: people (read: women) who are expected to manage their families and households during their non-work hours are impacted by these attitudes disproportionately, and men who don't have to do this are often supported by women who are doing those tasks for them.


Zombie thread response, but I find this an offensively dated view on families.

I have managed my two young daughters on my own and still manage time to code, read and learn about technologies and many other hobbies.

Where do I get that time? Aside from the weekends (when I sometimes teach them), typically after my children go to bed. It's probably during the average 4-5 hours that other people spend watching TV.

I'm not saying that it should be mandatory, like anyone else; that was your leap.


Let's see...

If you work 40 hours/week and sleep 8hrs a day, you only have 8 free hours every day. Discounting the time that you spend going from/to work, the time you spend on meals, personal health (physical and mental), housework etc, how much time is left? In my opinion, very little.

So yes, I prefer to spend this time on my other hobbies. Of course I study by myself, take some online classes, read articles... but I don't allow this to take the most of my free time.

Getting other hobbies opens your mind. Socializing with your friends is important to be, more than a better employee/coder, a better person. If you have a family, even more important to spend time with them.

Life is too short...


While you are seeing it as a passion, your co-worker see his job only as his, well, job. He may like programming but want to keep it as a job and not as a hobby.

His vision may differ but in the end, through his professional projects and contacts, he will learn and hear about new techs or languages. So, I don't think that devs like him will only stagnate, maybe just learning slower than you.


I program at home for fun all the time. I don't work on work stuff at home, because that would defeat the purpose of destressing.

One of the things I enjoy doing is learning new languages. I try to learn a new one, every year. (This year had a bit of a detour, since I planned on learning for Swift 4, but have since had to shift gears and learn C++11 and C++14... lots of changes from the world of C++98.)


I like to learn other languages too! My main problem is that I don't commit enough time to different languages to make useful or interesting projects out of them.

I've been trying to learn Dart and Go for some time now.


If I had no other responsibilities I would certainly spend a lot more time coding (and I did back when I was more free -- before I was an elderly 26 yr old). However ever since my son was born there has been very limited free time for any hobbies, especially something as isolated (from my family) as programming.

All that is just to say that each person has different responsibilities and interests so I would never discount anyone who only codes at work. I would agree with other answers here: 40 hrs, well spent and focused, should be plenty of time to practice the software trade.


Not being passionate about your work is separate from having side projects. I don't really like working with people that aren't passionate about what they do. I don't want people to be overzealous crazed idiots, but showing at least respect, interest, and care for your work are important. This is especially true for fields like programming where there is too much freedom to just coast along and get good results.

As to side-projects, if I worked on my side-project full-time I wouldn't do programming on the side. But I do now, since it's a challenge and programming is what I like. You should make sure your side-project is something you like, that's far better than forcing yourself to do it just for learning sake.

Having any kind of hobby is important though. It makes you a more interesting person. Whether the hobby is programming, photography, or anything else, doesn't matter much, so long as it does something that enriches you, and those you interact with. (I'm also a masseur as a side-project, it's a great contrast to programming.)


I identify as a programmer who doesn't program outside of work; save for the odd bit of tinkering once in a blue moon.

While you can call any given person in our line of work a "programmer", I believe there is an important semantic difference: "coder" vs "developer".

For a coder, programming is the job. It's a systematic routine; read spec, produce result.

For a developer, programming is only part of the job: Along with design, project planning, deployment, operation, support, etc.

Personally, I fall on the developer end of the programming spectrum. While I don't necessarily breath, eat and sleep code all hours of the day; I do take problems/ideas home with me mentally to mull over evenings and weekends. The time to put those thoughts into code, however, is at the office.

This is what works for me, but as with anything, we're all individuals, so my spin on things isn't necessarily something that will work for another (or that another will even agree with in principle).


I love programming, but I have other hobbies and I don't typically want to go home and do the same thing I just did for 8-9 hours at work. My brain can rarely being "on" for longer than that each day.

Every once in a while, a fun side project will come along, but with one real exception, it never sticks long.

For some added context, I'm a self-taught developer who turned programming as a hobby into a career.

Anyway, it really angers me when I see programmers being judged for not being waist deep in programming 24/7.


I have a wife, a plethora of hobbies, and a salary that lets me enjoy them comfortably. I used to code a boatload when I was in college, but once I graduated, I found that most jobs didn't give a crap what I could do with , they wanted to TRAIN ME to work within their code base.

Right now, I'm spending a ton of time at work ripping out a ton of random JavaScript framework junk that someone implemented "because they knew it really well", without any thought as to how the business would be impacted.

Stop pushing this disgusting thought process. We don't need to live and breathe code to be successful developers.


Programmers are hard workers by nature, but we should stop judging people by their time work spending. Balance is health. Maybe for you coding at home is okay, maybe for others coding at home is toxic. It depends of the personality of each one. Personally i prefer do exercise, cook, read or fill another area of my interest. If some day i find an idea or project interesting i will programing at home.


I would love to be one of those programmers who code at home on a cool project. But the simple truth is that i have not come up with a good idea yet.

Apart from that, id prefer a colleague who has a working social life, does some sort of sport and has other interests than coding too.


IME the majority of people work to live, they don't live to work. Programmers who are passionate about programming are in the fortunate position to earn a living doing something they love. That's great. But there are millions of people in the software field. It's unrealistic to expect all of them to be passionate about programming.

A happy life usually means a balanced life. Doing the same thing 24x7 doesn't sound balanced to me.

That said, programming and related disciplines are not "just a job," they're a profession. Any professional has an obligation to keep up with new developments and keep their skills sharp. That means a professional programmer has to invest some personal time in career development. It doesn't have to be 24x7. There's plenty of space between the person who is bored at work and can't wait to get away from the keyboard, and the passionate developer who can't get enough programming.

I usually advise younger colleagues (who ask) to decide how much of their own time they're willing to invest in their own career growth, and plan to learn about specific new advances in the industry that they think will be of value to them going forward. It isn't necessary that they subordinate their entire lives to their work, but it is necessary that they do more than just show up at work.


Do not forget the people who take work to home (it happened to me more than once)

I think that is nice to have passion for your job, but also relax is important. Stress could be a serious problem, and designing/coding/testing are complex tasks that demand too much patience and thinking, so you could burn out easy.

Enjoy coding, learn and work with the technologies that you like, but also take your time for your family and friends. More is not always better


I used to enjoy coding at home, and I still have a lot of ideas I get enthusiastic about, but I rarely write anything outside the office other than a quick hacky script to automate something anymore.

This is partly because the things I want to write aren't significantly different to existing projects, partly because I know from experience that it's just going to be for my own amusement rather than anyone else.

What I do a lot more of is hang out on help forums, SO, places like that. I spend more time updating wiki pages and doing the sort of zero-friction documentation you can help out with while the pasta's cooking.


I really enjoy coding, it's why I went into a career as a coder, but to be perfectly honest, after 40(ish) hours of sitting at a desk coding in a week, I find it requires a supreme force of will to come home, sit down, and then do more coding, because it feels too much like work. (Tips on how to get around that are very welcome!)


TLDR: I have several experiences.

I have a reputation of having a very disrupted work/life balance. One could argue that there is no balance and my live is spent behind a computer, with occasional dancing and partying of course :) But my main focus is writing code or just making stuff that I just can't keep inside. I have pain in my left thumb, from making that SHIFT key go down every minute. My shoulders are tense and my knee sometimes hurts like I am 80 years old. That is retarded, but it is not as bad as I paint it with words. SO I WILL PREVAIL!

To come back to to what you are asking... I have seen them.... on the workfloor.... ... ... ... .. .... ..
..... (heavy breathing)...THEM!! AAAaaaaah the horror.

Only kidding of course :) I had good and bad experiences with 9 to 5 programmers.

The regular: I had colleagues who did frontend stuff. Learned some at school and when applying for the job they knew some Angular 1. The did what was expected and we finished sprints. Their code gradually improved, because that is natural.. I hope. At some point you get organised or lost, so trying to get a little structure is helpful. Kicking some design patterns into view and it looks daunting at first, if the colleagues are human and reasonable, they will form their own opinions and it will improve their code.
They went home at 5 and came back in the morning. No stress. This is how most developers live I think. It is just a job, like being a fireman/woman, toiletcleaner, whatever. And it probably is a very good way to think about your work.

The good: One colleague was really open for whatever. I worked hard and was really good. He did not read or play every evening, but once in a while he needed to pick up something in his free time. But in general, he learned and worked at the job. I liked that. Very straight forward and a good problem solver. He liked structured code and did not drink the Kool Aid. He was een independent thinker and not a cargo-culter. I personally like these kind of colleagues. Pretty balanced.

The sad: Another colleague worked at this office for his entire professional career. He thought himself all knowing. He never picked up new things and everything he wrote was just to fix it quick. Cowboy code. The cowboy kicks in the door of the bar, shoots holes in the ceiling, drinks all the booze and takes all the girls. It was horrible. He was the authority in the company, so he put his VETO on everything he did not know.. and that was a lot. So we could not have nice things. Aaargh what a devil.

We need different types of people, because that makes the world a fun and crazy place to be.
Originators, rebels, stubborn cows, slackers, ploughers, regulars etc. Keep it up folks.

It is all fine, except...

Never become the sad or become the passionate developer who forgot that life happens offline.

Everybody in the technical workforce(doctors, dentists, hackers, deepsea drillers, car mechanics, etc) need to keep their knowledge up to date. Do this how you see fit, but make sure that when you move from job to job, that you are still relevant. Be as relevant and useful for your boss/field-of-work at 20 as well when you are 60 years old. You will need to work until you retire.. or marry a rich woman/man.
Stay relevant.. and if you want to freak out on books and techniques.. well go for it and become the teacher or 10x developer people talk about.

10x means that you can make the people around you 10x better.
Don't write all the code yourself. Hero's are bad for the team. You, the passionate one, writes enough code already. Use the things you learned from your passion and help those who can not spend as much time as you become mofo elite h4x0rs :D


I'm a "non-trad" programmer, as in I was a professional musician/teacher for a decade after I got my Master's degree in Jazz Studies.

TBH, I feel like I need to study/code outside of my job because

  1. I am by no means a master of my craft and have a lot to shore up for where I want to be professionally
  2. Competition is real

I really like coding, don't get me wrong, but I know there are plenty like me that don't LOOOOVE coding. It's an interesting job that pays a hell of a lot better than any other job I've had. That said, for me it's a job. I'm not trying to do my job 100 hours a week.


Tech moves FAST (from my perspective). Maybe I'm paranoid from my "starvation days", but I'm afraid of getting comfortable in a technology and getting left behind. I'm also curious where tech is going as an industry and want to be a part of that change. I'll tell you, though, learning new things at 38 is a far cry from learning new things at 23. It takes concerted effort and concentration, IME, which does not always happen 9-5.


I feel the same way. The fear of being left behind or being ineffective is real.


They are doing a great job too, they are constant delivering tasks and fixing issues. They are patience and do not have to focus on the big picture. You need them in mature products. They usually (from my exp) do not want/or have time to improve their skills and knowledge, only if needed or are exposed to them (office workshops, new procedures and tech).

You also need devs that push the boundaries and search for future problems and find solutions for them, devs that try to optimize the product, processes and workflows.


Do I code outside of work? Rarely. Mostly it's just testing out some theories rather than full-blown side-projects.
Does that make my any less passionate about programming or the industry I'm in? Not in the least.

I'm at work surrounded by coding, design, architecture, business discussions all day, 5 days a week, most days over 8 hours. While I don't always have time to be dabbling in the latest and greatest, I'm always looking for how I can improve. I'm always testing out new ideas or finding a day here and there to work on some not-quite-necessary, but would bring benefit to our daily work types of tasks. This is what keeps me refreshed and recharged.

After sitting and staring at a screen all day, one of the last things I usually want to do when I get home is to sit back down at a computer and keep coding. More often than not I'm spending my time outside of work reading tech blogs such as these, searching for new concepts and soaking in the as much as I can. It's from this that I can then form my own ideas and my own theories and often try to put these into practice at work.

It's not about how much screen time you put in, it's about how much heart you have. Do you love your family any less if you don't see them every day? Probably not. It's because it's a part of you that you know you can always go back to. It's not escaping, it's just finding out what works best for you.


Side projects are time and energy consuming, and they need funding. I mean side projects that are not just toy projects, but actual useful projects used by a lot of people in production, and maintained for a period of at least 3 years.

Most of the people lack the motivation of doing such a prolonged effort, beyond getting the next paycheck. And that's fine!

And yet we use tons of free OSS projects daily. But I'll tell you something - these projects are not free for everyone! Certainly not for the ones who create and maintain them.

But that's not the point either. It's about whether you want to contribute to the broader community in some meaningful way, without expecting anything in return.

The OSS side project rabbit hole is rather deep, you just have to open your eyes to see it.


I love coding and I love my job.

However, I'm not a huge fan of coding at home. I have tried but I get distracted by other things. I quickly jump to learning other things: reading about woodworking and tools, watching tutorials about Affinity Photo and then try use those techniques on random photos.

I have also started a music and video production company with my buddies so I often find myself writing the next song. Here is my shameless plug for our first music video youtube.com/watch?v=r2ZC3aA4MYE

My wife and I love taking small random trips. We love food so we often try to find something new to try.

All of these things have played significant role in my personal growth. Oh and I am not a huge reader of books but lately I've been spending 15-20 mins reading Clean Code before going to bed.


I don't enjoy programming at home, either. The reason being that at work I don't have to maintain my tool chain alone, I get inspired by my co-workers and get tasks from the business that are actually challenging.

Not coding at home doesn't mean I am not passionate about coding. I constantly learn: Reading blogs, answering on Stackoverflow, watching videos, attending user groups, unconferences and conferences - most of it in my free time, on my own budget.

I can completely relate to anyone who separates work from private life. It's just part of the contract: I get paid for my time at work, and my task is coding, so I code during work time. When work ends, I am free to do what I like. If I don't like doing more coding, that's fine. That however does in no way tell anything about passion.

Can people improve that are not passionate about what they do? Yes. It'll probably take more time, and maybe they don't reach the top level - but this can even happen to the most passionate folks if they have the passion, but lack the skill.


I see no reason why someone isn't capable of being an awesome programmer and also not being very into it.

But if I were hiring someone to build something for me and I saw one person who loved building those things and was genuinely passionate about it and another person who seemed more "meh, it's a job" about it... I'd pick the passionate person. Especially if I were creating a team and wanted to foster a culture of people who are passionate about building that thing.


I can't imagine forming an opinion of a developer on this basis. I understand loving to code and think it's entirely reasonable to work on side projects outside of work. Sometimes there is no better feeling! But I also understanding having a family, friends, volunteering in a nonprofit, and having hobbies that are not coding. So while I'd never criticize someone for coding in off-hours (and I think the surgery analogy is unhelpful here), it is incomprehensible to me that we require that the only way to be respected in our profession is to want to code at night and on weekends and have a life arranged such that it is feasible to do so. Madness.


Your eagerness to work in your free time will slowly fade only if you are not doing the things you are passionate about. That's why many people become entrepreneurs, instead of being enslaved by someone, because then they have much more control over their lives.

It is very easy to get stuck in the stage of constantly solving problems or learning something because during that process our ego rises and it feels enjoyable, that's why some people who are married to their computer do not need much / any social interaction. The question here is what is your life's purpose (hopefully, you have one) and are you actually going after it, clearly seeing it in front of yourself when you meditate and work or coding it just a way of escapism from the real world for you as it is with many developers (which may feel natural, but again, take away the distractions and activities that boosts ego for few months and you will see what you actually as a human being are without them).


I think it's more about continued learning rather than coding outside work. I've worked with developers that would not try to learn anything new beyond what they minimally needed to do their job. They obviously did not code outside work and usually were challenging to work with. I've worked with other developers who were passionate about programming, reading about and trying new things. Although many of these folks also did not code outside work either, they were usually a joy to work with.

And frankly someone who spends all their free time outside work coding is probably not a well-rounded individual and in the long-term I think that makes for a poor employee and co-worker.


Coding pays really well, so I wouldn't be at all surprised if this were the case for the majority of programmers. If you're good enough at it, I don't care if you enjoy it. People who are not super-passionate are often more pragmatic and focussed on getting the job done.

I don't think it has an impact on learning. It's the employer's responsibility to allow and enable learning during working-hours, and take care of mentoring. If you do 2-4 hours of focussed productive work a day, you won't have much energy left in the evenings, after all.

(I personally learn new stuff at home all the time, but that's because I enjoy typing code, not because I feel obliged to improve in my spare time.)


You can be very passionate about programming and not have side projects, but the inverse can also be true. I have side programming projects, but I also have many other interests which compete for my time. When I'm already coding 40 hours a week, it's sometimes hard to justify doing even more when I have an array of other things I'd like to do.

That said, if you don't at least find joy in programming at work, that would probably show in your interactions with colleagues and cause you to stagnate somewhat.


I don't like to talk about other people, I could certainly say how I use time away from work and what works best for me:

  1. I love to take some time away from programming when doing investigative work with hands on approach, it gives me 2 advantages : an opportunity to look at a problem with a fresh eye perspective and my brain can dwell on problems I might be needing to refine

  2. When at home, I suffer if I have ideas that I want to try and no opportunities to do so. I can sense that I stagnate when this happens.

  3. There are times when , in a discussion, one can just tell how many hours of practice someone has put into a skill, he might know about the technique, but their lack of skill shows and is detrimental to my productivity when in a discussion

That being said, I think we as humans tend to think less of people that don't put the hours in. I however love to lead people and there is certainly a place for people that know techniques in the teams I interact with or am part of.


My take on it is as follows,

For 13 years straight without missing a beat, I read every day. I practiced the exercises, even when I hit a sour point in my life (IE very sick) I still read. However I never felt that I was moving fast.

It was only recently that I realized that having a balance of home / work did I start to learn more and at a faster rate. I started to realize I only need to learn what I need to know to get the job done.

So I feel that to answer your question I fall somewhere in between. I will code when I feel and itch coming on, but other days I will spend my time having fun with my family.

I agree with the others that we shouldn't judge those that don't want to program 24x7 nor should we push for developers to do that unless we want to start burning people out at an accelerated rate


Work burns my brain out so damn much I can't do anything even remotely mentally-draining by the time I get home. Forced lack of sleep all week long doesn't help either. I have 9 side projects I want to do so far and counting, yet even gaming is too difficult! From time to time, I get a tiny bit of vigor back over the weekend that I manage to do a couple hours of side project work. It's just too much, when you're learning a completely new stack, new language, new architecture, new everything and doing it all at once, there's far too much learning and brain usage going on to allow room for anything else. Your brain needs rest too.

Needless to say, as soon as this project is over I'll be having my fun. Until then, I remain a slave making somebody else rich :(


There are a lot of things that are only possible coding at home, for example, the whole desmocene thing, most of the people that participate or just follow desmocene events have a work where they can't practice or create something related to the demoscene like intros, music, shader coding, executable graphics, etc... These things are learned and mastered at home.

What about the ludum dare? People participate in ludum dares from their homes, and that means that part of the team code a game at home (and propably they learned to do that coding at home first).

What about new projects published on github by individuals at their homes that eventually become well known production tools in companies (probably because someone tried it at home)?

What about people that wants to change their careers? I was coding for an insurance company for 5 years and I realized that I wanted to make videogames and get a job in the videogame industry, how do you thing I reached this dream? Coding pet projects at home of course.

If you don't code at home, you are a slave of whatever your job wants from you, you can not learn new things if your job doesn't require it, you can't improve your skills if your job doesn't demand for it.

For a lot of people coding just at work it's ok, and I'm ok with that, but coding at home It's a very valuable activity that even people that doesn't code at home get benefited from, and every time I will require to learn/try/practice/understand/master something that I can't do at work, I will code it at home.


Sorry to hear you still have not realized that you are destroying yourself by substituting sleep for anything else. I guess you are still very young and in case you care about your health and life expectancy, I truly hope that you will educate yourself better on how different things that average human beings do have negative impacts on our lives.


Sometimes only coding at work doesn't relate to the joy of coding, it relates to health, at least in my case: 8 hours at work, sitting. I need to reach 8000 steps or workout and then there are chores and stuff.

I must say it's true that I expend some more hours sitting at home, probably playing some game, something that doesn't need focused thinking, because getting 'in the zone' takes some time and it isn't something you can quit anytime or to switch constantly, at least if you really want to acquire new knowledge. So, I'm currently struggling to code at home, I might seat once a week maybe, it's life or I'm just a mess.


Well, people are heading towards simplifying just abt everything in computer science nowadays which makes it sooooo interesting to read beyond programming. I am a programmer and I enjoy building n reading abt devops solutions when I am not programming. Does this makes me bad programmer ? Dunno, but I enjoy what I do. Even of I am not doing anything, I read snippets abt all the cool stuff ppl r tweeting abt in computer science.


I personally love to code, but I don't want it taking up my whole life. I feel like there's a huge stigma that if you're not constantly coding, it means you're lazy to learn. I spent majority of 2016 learning new things, joining all the hackathons I could, and building up my portfolio hoping to get noticed. And I did--I landed a job at an amazing company while I was on my last year of school. But now, I feel like if I strive for the same amount of work I did last year, I would burn out.


I've contributed quite a bit to FOSS over the years and have several "passion projects", but I don't think that "has no side project == has no passion for programming" is a valid assertion. Not everybody lives to work, and I have some very talented friends who are good programmers, not least because of their varied interests that they pursue outside the office.

I'd much rather have a dedicated developer who gives 100% at work and then goes home and lives a happy balanced life, than someone who burns himself out in the first couple years on the job. When you're in your 20s you seem invincible, but now that I'm almost 40 I deliberately do less and often pick recreational activities like language learning, drawing, playing video games, or watching movies over weekend/evening coding sessions.


Can you be a coder and only code at work? With the proliferation of hundreds of frameworks, the never-ending list of new languages and the pressure to be successful; Can someone, just starting out, afford to only code at work?

Not saying you can't. Personally, I like going home, working on 3D animation, or playing my guitar. I have side projects going and want to start writing more.


One interview question I read about: Do you have a tech blog or a GitHub project?

When I read that I did not.

Also, I envisioned a horrifying follow-up to a No answer: Is that because you don't want to share? Or because you don't have anything worth sharing?

So now I have a blog and a GitHub project, both of which I thoroughly enjoy working on.


I find the question is representative of a kind of company culture. The startup-mentality, go-for-broke type companies are looking for "ninjas", "superheroes", "geniuses" and so on. They want their employees to live and breath their work, and if we're not being particularly generous about it, they want this because it benefits them. Remember that if we're talking about full-time engineers, these people are doing somewhere around 30-40 hours of developmental work a week. That's a significant amount of time learning and improving as one solves problems and exercises their muscles. I would suggest stagnation would only occur if you got away from development entirely - say if you moved into a management and were organizing a project rather than spending time in the code.

I know lots of people who work at work and do other things entirely at home. One thing I want to bring up: The question asks if people who don't program can continue to improve. If we answer yes, then we're biasing towards people who have the time and energy to do so, and saying that those who don't have no hope of growth.


I have no opinion about them at all, people do jobs mainly to make ends meet (programmers included) and you shouldn't judge anyone who wants to have code-free time outside work.

Not all programmers are passionate programmers, and that is completely fine.


You can love programming without wanting to do it 24/7. Personally I quickly burn myself out if I let myself program in my free time, so I don't (well I do, but rarely). Instead I focus on other interests, like art or writing or reading, though sometimes I write or read about tech topics. It's important to do things other than program, if only so you can apply those skills to programming and give your brain a break from a difficult problem.

I do think there is a certain amount of passion necessary to become a great programmer, but if you're programming 40 hours a week and not seeing improvements in your ability then there's something wrong.