News for hackers. Stuff that matters.
Re:Exercises to craft an employer brand that makes engineers... by newfangle on Tuesday May 14, 2019 @01:24PM (#19911500)
You go from 30 to 35 straight to 60 when im thinking 40 hours a week. I dont know about you all but if i work 5 to 10 fewer hours a week i would get a lot less done
Re:Exercises to craft an employer brand that makes engineers... by tass on Tuesday May 14, 2019 @01:29PM (#19911565)
Have you tried it? I am definitely tired and have generally hit a wall after about 6 hours or so. If I call it and stop, I’m fresh for the next day.

If I instead stay at my desk consistently, my week is over by Friday morning.

Re:Exercises to craft an employer brand that makes engineers... by avgDev on Tuesday May 14, 2019 @01:54PM (#19911942)
60 hours is a joke, I have done 60 hours handful of times. When I was young and when our all systems got hit with ransomware and I was helping out the IT dept.

I agree and think 5-6 hours is the magic number. Then, I start making errors, taking shortcuts and producing shit code. However, if someone is a super human and can code for 60 hours every week, breath code and make $400k at some unicorn all power to them.

In reality, after $75k your happiness will generally not increase very much if you increase your income.

Re:Exercises to craft an employer brand that makes engineers... by eropple on Tuesday May 14, 2019 @01:28PM (#19911558)
I find that my productivity, when I am specifically constrained to 30 or 35 hours a week, doesn't really change--because it puts a clear value on my time to other people.

Or, put more simply: I end up in way fewer meetings.