I feel like its difficult to quantify for jobs where you’re being paid to think. Even when I’m goofing off, the problem I need to solve for the day is still lingering in the back of my head somewhere. Actively squinting at it doesn’t seem to make things go any faster and when I do return to work it’s usually to mash out reems of code after letting it stew, but yes, the actual amount of time I’m fulfilling my job description is… less than my working hours.

Anywhere from 1-7 depending on my mood, how many “useless” meetings I have, how many interruptions find me, how you want to count the questionable-usefulness meetings, and how long I look at slack/email/etc or just thinking about work while at the bar.

About 4 ~ 12 a day, though roughly about 50 ~ 60 hours a week.

A 4 hour day would be if I have some problem that I know has a good implementation, but I just can’t figure out how to do it. Then it’s better to just stop and do something unrelated.

Though then once the problem is solved and all the puzzle pieces fall together - and I can just work on implementing it, and refactoring it into a good solution - I can continue working on it without caring about the time.

But I don’t have a lot of days where at the end of the day I’m like “Yess, I’m finally done working, now I can start doing something fun!” - The working itself is already fun, so that creates a different “Working vs Not Working/Having Fun” dynamic