It's not so much that we can't accept that some people enjoy working, it's that they're screwing their health. There is no free lunch, staring at monitors for years on end will take its toll.
Gaming and watching TV aren't healthy for computer workers either.
No, rather a computer is a general purpose device on which I can make music, listen to music, edit video, watch moives, learn a new language, look up recipies, talk to friends, chat with experts on all kinds of topics. I don't stop using the computer "because I use it at work"
The same is true of programming and side progects. Programming is not work. Programming is something I do at work like I alos talk to people at work, sit at work, walk at work, eat at work, write emails at work, chat at work.
Programming is also a fun activity in and of itself I get lots of enjoyment out of just like I get enjoyment from those other things. That fact that I do it at work as ZERO influence on my enjoyment of it. I might not enjoy certain things I do at work but that has nothing to do with "programming" and everything to do with goals or don't believe in or busy work for the sake of busy work or having to do things someway I don't agree with, all of which disappear on my own stuff.
I think that's totally awesome =]
However in the post itself, the reasons listed for doing a side project include making money and learning new skills. One of those things is literally the thing that defines work, and the other is something that many would assume is for work.
I believe that's where this animosity towards the expectation of side projects comes from. If you want to do it and would do it without any benefits to your career, then definitely it is purely fun and in the same class as meditation or hanging out with friends. However, if you argue that you should do it to make money, personally I would say that's no longer in the same class of things as hanging out with friends.
Indeed programming for the sake of learning and programming for the sake of enjoyment are two different things I'd say. It's like when people comment how it must be so relaxing to practice piano; no it's probably fun and relaxing to play but practicing is very boring and frustrating.
The computer is a tool. It's the tool that I use to create things, and that creativity gives me life. I don't think people without creative hobbies can really understand this.
From my musician friends too, I seldom see them ever spending more than 8 hours a day doing music. As music work isn't really 9 to 5 style.
Here we're talking having done an 8 to 10 hour day programming, Monday through Friday, and then spending even more once home and on weekends.
Now, I happen to be, maybe as you are, someone who is passionate about CS. So I do actually do it as a hobby and as work. I just don't believe everyone should, and I don't want to make it the norm that you have too, because if that was the case, my doing it as a hobby for myself would now become me doing it cause I have too for employability.
It's also not my only hobby, I found that when it was, it did in fact slowly overwork my mind. I'd slowly start sleeping later, waking earlier, having issues falling asleep because I'd always be thinking about my problems. A few hours before bed, switching to a non thinking hobby has been really nice for me.
I agree with you about the stigma though. I think if anything, I'd like to encourage non-programmers to pick up programming as a hobby. It's a great creative outlet, and the computer is a tool. It can be very rewarding and so much fun. Plus, for many, it could translate into a better career for them.
As a programmer though, I think it's just up to you, but definitely you shouldn't have too.
Just my opinion.
The programming "interface" is more or less staring at text on a monitor and clicking on buttons. All the creative work is hidden and the interface is complete crap... How can that be perceived as fun or creative by someone looking from the outside?
Music making always had an aura of coolness, so even if a professional musician were to do that, maybe people would not see it as work.
When you get money for programming, that's work, but programming in itself can be both fun and work. A side-project you do for yourself should be fun and exciting.
Especially if it'a a side-project, which implies planning and goal setting. Of course if one is just aimlessly messing around then it becomes less like work.
I'd say it's nothing like work. There's no stress, no deadlines, no fixed hours, no team work, etc. For many people programming is a hobby, something that's fun and they are not paid to do, they don't do it for the money, but for self-fulfillment. Not everyone find that at work, and even if they do, they may choose to spend a few hours a week building something for themselves, to scratch an itch or whatever.
> It's not so much that we can't accept that some people enjoy working, it's that they're screwing their health. There is no free lunch, staring at monitors for years on end will take its toll.
I doubt 50hs of screen time is a lot worse than 40hs, but I'd need data to prove/disprove it. However, you don't even need to spend that much time, it could be just a few hours a week.
https://letterstoanewdeveloper.com/2019/08/02/personal-proje...
It seems to me that you can treat side projects like work, but you shouldn't. Side projects should be about scratching an itch that can't be done at work, whether that is the domain, technology or some other aspect.
If your side project is like work, pick a different side project.
If every side project is like work, as is so for some commenters, then take some time off from them. Or don't do them and forgo the benefits.
for you it is, for me and many others its fun/hobby. This is why side projects are such a strong signal to competent recruiters -this person actually likes what he does and will put passion into his work.
I could even make a case that people who don't spend their free time coding make better employees than those who do - the employer wants the employee to spend their mental energy on work, not personal projects.
The vast majority of people who are going to give you a high quality 9-5 aren't going home to program, and it would be very bad business to discount them.
(The only person I knew of who coded outside of work was honestly a bad employee. I wouldn't use that case to discount others who code for fun outside of work.)
Although that could be just me, I think it's a common problem.
Work is what I am paid for. Anything else is either your human needs or hobbies.
I prefer a colleague's response to my question whether he has side projects: I don't like to do the same as I do (at work) here when I am home.
It's an incorrect answer, but at least it doesn't imply side projects are work.
Grab a dictionary and you'll see something along "activity involving mental or physical effort done in order to achieve a purpose or result".
Unless your side projects have no purpose or goals, they are a form of work and they require effort.
Since I'm working 40h/week as a software engineer I find much less motivation to do PC related stuff (this includes gaming). That was different, I used to do random programming after school just because I could. During university this became less. However, I do enjoy most of my work, so there is that. And this is why I originally started studying physics - I wanted to keep programming as a hobby, but figured out I probably wouldn't really enjoy working in physics and then switched to CS.
Regarding health: I think with this you're wrong. It depends on the "how much". Staring at a monitor 8h at work, driving home, stare at a TV/monitor another 6h munching fast food, go to bed, wake up, repeat; this is probably quite bad. But get home by bike or foot (if feasible), program/game/watch TV for an hour or two, go outside, do some sport, reduce unhealthy food, and you can probably get by quite fine.
Well, I still do code as hobby.
The thing is writing code for company is not always fun, for example, your company use React and you want to try Vue, the only way to do it is create hobby projects of your own.
And there are other benefits as well, for example, if your project is useful, it may open new opportunities for you, showcase your abilities, let you make friends and maybe even allow you to directly make money from it.
> I find much less motivation to do PC related stuff
Me too, sometimes. But personally I usually found the main reason for me to lost motivation is when I realized the project I'm working on is useless -- No body will use it even I released it, so I just stopped working on it.
But you know what, some of my abandoned code can be reused when I have new ideas, so I count all of it as sleeping gold (Or maybe sleeping bug, depends on production results :)
No, work is work, side-project is a hobby,it's done for recreation, for example to do some stuff you can't find a reasonable excuse to do at work. To explore and enjoy yourself doing what you love. That's also the only reason to have one..
Doing _ANYTHING_ is work if you look at it wrong enough.
Work doesn't just refer to performing a job in exchange for money.
Even the term side-project contradicts the idea of leisure. It implies goals, a plan of action and tasks that have to be done.
Professional programming sometimes diminishes the passion, I have to have side projects to keep it alive.
But I agree, there are ways to balance things, but you have to choose. You can't have everything (work, side project, family, health, hobbies) at 100% and be the best version of your self long term.
I agree, but... I used to do them for fun, for the challenge, to learn, to prove to myself that I could do it.
I've recently been working on an existing open source project. I do so because I like the software and want it to be better. I also have the background to contribute in areas that haven't been touched in years. While its voluntary and feels like a side project, it's still work.
These things are all work, it's just a question of why we choose to do them. Maybe the other commenters that dont see it as work have a bit to learn about their own motivations?
