Most days* : 5:00am - 10:00am * OS development * puzzles * articles * work on personal projects 10:00am - 6:00pm * coding for my day job 13hr/day * 5 days/week = 65hrs + anything I can sneak in on weekends I aggressively work on work/life balance and take frequent breaks (a great habit leftover from my days as a smoker), so I don't spend much time staring at the screen -- I use this time fairly efficiently. * I'm get…
But you listed "puzzles' in your work, and you included your lunch and co-worker conversation time, unless you're always in front of your screen, zero distractions. If we're all counting all that time, then that changes these numbers a lot. We really need to clarify what 'work' is for these numbers to be useful, at all.
How granular do we get in defining what qualifies as a "work hour"? Do we not count bathroom breaks? The time it takes the computer to warm up? The milliseconds between keystrokes? "Work hours" will always be an issue of semantics. Here's my definition: any time I'm not dragging my feet about accomplishing a work task. Here's my tautological definition of a "work task": a task I perform for work.