[zoggenhoff]

I work in devops. So I can easily have quiet developer time and operational issues appearing out of nowhere. We're used to this mixture. "Crunch time" is only for short term thinking.

So, in a perfect day, do you want to be an employee mashing the keyboard all day with no break? Or just sitting there staring out the window? Logically both extremes are unrealistic.

Now, choose a reasonable mixture. Does that look like 75% mashing of keys / coding / meetings / etc and 25% staring out the window? Maybe it's 90/10? Or 60/40. No perfect answer exists: the only answer is "it depends".

A work week is not a sprint. It's more like a marathon. Each checkpoint is to be met. Slow down or speed up as necessary. This is how I experience dev ops. Some hours of a week are "get it done NOW". Others are "do nothing - all is calm". A few are "we'll need this next month, need to make some progress today". Plenty are "end of week" or "end of day" style tasks.

Results matter.

[cjamesd]

Interesting response. My take-away is to optimize for more than just a given day, because not all days/weeks are created equal in their demands. Thank you.