Live data from Hacker News

It's okay to code on nights and weekends

tej.as

81–87 of 87 posts

Re: It's okay to code on nights and weekends

#82
post #37
post #8

I would love to code more on nights and weekends, but if I spend too long at the computer it makes my body hurt and feel bad.

I work a remote tech job and despite taking 15 minute (or longer) breaks every couple of hours, I have come to the conclusion that sitting in front of a screen for 8+ hours a day is slowly killing both my mental and physical health. I am trying to combat it with strength training and cardio in the mornings, and spending at least some of my evenings in my garage. This, unfortunately leaves me with very little time to…

> sitting in front of a screen for 8+ hours a day is slowly killing both my mental and physical health

Do strength training when you are stuck waiting for things: tests running, mandatory meetings where you only listen. I have a set of dumbbells and kettlebells next to my (WFH) workstation and put them to good use during most working days.

Re: It's okay to code on nights and weekends

#83
post #69

The main reason not to code on evenings and weekends is that your employer will own everything you do and might not allow you to do whatever you want anyway.

What? Do you know you can code for yourself and not for your employer?

I think the GP is referring to practices like [1] "Google claims copyright on employee side projects".

[1] https://news.ycombinator.com/item?id=21823413

Re: It's okay to code on nights and weekends

#84

Earlier quoted context omitted.

Have you never considered the absolutely /terrible/ manners of showing up to a profession where other people are passionate about what they're doing, doing the best work they know how and enjoying it - and then complaining because you only want to phone it in for a paycheck? Perhaps you chose the wrong line of work... Not everyone has to be a programmer. Not everyone is entitled to be a programmer just because they w…

According to you, is it possible to do a programming job well while not deriving enjoyment from it?

I think it is possible however it seems you don't have much incentive to explore more than you need to. Which might be enough to do your work well, but I don't understand that you wouldn't want that. I build stuff all the time, weekends, evenings and try to implement new things I never did before. It's fun and handy for later.

Re: It's okay to code on nights and weekends

#86
post #69

The main reason not to code on evenings and weekends is that your employer will own everything you do and might not allow you to do whatever you want anyway.

What? Do you know you can code for yourself and not for your employer?

Any employer that pays decent money will claim ownership on everything you do even if you do not use any of the company's resources to do so.

Re: It's okay to code on nights and weekends

#87
post #69

Earlier quoted context omitted.

What? Do you know you can code for yourself and not for your employer?

Any employer that pays decent money will claim ownership on everything you do even if you do not use any of the company's resources to do so.

That's absurd.
Post reply on HN