The Programmer’s Guide to a Sane Workweek
codewithoutrules.com
The Programmer’s Guide to a Sane Workweek
1–10 of 152 posts
Re: The Programmer’s Guide to a Sane Workweek
#2I think this really boils down to self regulation. In some/most cases no one is forcing you to work 50+ hours a week.
I remember a sign a coworker used to have in his office. The gist is - are you happy? If so, keep doing what you're doing, if not, change something.
Re: The Programmer’s Guide to a Sane Workweek
#3Just put in my two week's notice yesterday. I've been putting in a stupid amount of hours (80+) while my colleagues in other departments barely hit the 40 hour mark. This is a good omen.
Re: The Programmer’s Guide to a Sane Workweek
#4Finally, you'll need to have the self-confidence or stubbornness to choose and stick to a path that most people don't take.
You don't need self-confidence or stubbornness, just commitment to your principles...
I have never worked more than 40 hours per week for anyone else. Ever. I arrive at 8. I leave at 5. I don't work from home.
Except for emergencies.
My definition of emergency: If someone is dying or their production software isn't working. That's it. Anything else, I'll be in all day tomorrow and will be happy to talk about it then.
All you really need to do is reach an understanding with your manager about your boundaries and the definition of "emergency" at the beginning.
If they want to pay 40 hours for more than 40 hours of work or have a different definition of emergency, they I'll work somewhere else.
It's really that simple. I've been doing this for almost 40 years and have never had a single complaint about it.
And I'm not sure which "most people" OP knows, but "most people" I know have a philosophy similar to mine. We'll do whatever it takes to get the job done, but we won't be suckers.
OP, do you really need a whole book for this?
Re: The Programmer’s Guide to a Sane Workweek
#5I went to a talk once on leadership. One of the suggestions was to get your "go to hell kit" ready. That is, get enough money in the bank (whatever that means for you) so that you can walk away if things cross your personal lines, be they moral / work-life balance, whatever. It's a good thing if there's pressure to work silly hours. In my first job (recent grad) before I left the job, I'd been working 5 weekends straight (at least a Sat/Sun). Looking back, insane, now I'd be having a conversation with my manager.
Sometimes it's hard when the "norm" is to work these extra hours. Where I live now, I have worked a normal 8:45ish to 5:15ish and haven't had to stay late or work weekends in years. It can be like that, I reckon it _ought_ to be like that. If your contract says 40 hours a week, why would you work more? You're just reducing your hourly rate. Now, I don't mind putting in extra effort if needed, no worries, but if it's the culture that it's just long hours, well that's crazy.
Re: The Programmer’s Guide to a Sane Workweek
#6Just put in my two week's notice yesterday. I've been putting in a stupid amount of hours (80+) while my colleagues in other departments barely hit the 40 hour mark. This is a good omen.
Was that down to yourself or your employer ?
Sometimes we are our own worst enemy.
Re: The Programmer’s Guide to a Sane Workweek
#7Finally, you'll need to have the self-confidence or stubbornness to choose and stick to a path that most people don't take. You don't need self-confidence or stubbornness, just commitment to your principles... I have never worked more than 40 hours per week for anyone else. Ever. I arrive at 8. I leave at 5. I don't work from home. Except for emergencies. My definition of emergency: If someone is dying or their produ…
The article is also about going below 40h/week which is more challenging. I'm really happy to currently having an interesting 24h/w job with just enough pay to get by, but I'm currently also writing my thesis and definitely couldn't afford a child.
Re: The Programmer’s Guide to a Sane Workweek
#8Finally, you'll need to have the self-confidence or stubbornness to choose and stick to a path that most people don't take. You don't need self-confidence or stubbornness, just commitment to your principles... I have never worked more than 40 hours per week for anyone else. Ever. I arrive at 8. I leave at 5. I don't work from home. Except for emergencies. My definition of emergency: If someone is dying or their produ…
most people just don't have the balls to draw a line and not cross it, mainly because of fear. simple as that.
Re: The Programmer’s Guide to a Sane Workweek
#9The problem is never more working hours. Nobody minds working extra hours as long as they are paid for it.
The problem really is companies expecting people to do far more then anything they are ready to pay for. Sometime its even more worse when a few people have to make up for other people, and then watch the lazy group get rewarded better for political reasons.
The real issue is resentment not extra working hours.
Re: The Programmer’s Guide to a Sane Workweek
#10I read up to the part where he said he worked at google, then shut my computer down and jumped out of a window.