Work != presence. In a role in which you don't have to sit in front of a computer, 3h presence could mean 8+ hours of work.

I typically start working when I step into the shower in the morning. (I have a typical coder job.) Thinking about what to work on today, remembering the problem I left off yesterday (having parked downhill), etc. It's a great distraction-free environment. Some of the best ideas come there. No slack, no email. No CI pipeline that screams at me. Sometimes I keep thinking after the shower before turning on the laptop. Just sitting on the sofa. By the time I log in, I may have already worked for an hour. Or perhaps two, if I started thinking about work right after waking up. On office days, I typically think work during the commute. There mostly, but often even on my way home. I think that all counts as work hours.

Seconded. My daily walk to Starbucks is my time to meditate on my coding issue of the day, free from distractions of emails, office visitors, and meetings. Many coders I’ve met say a change of scenery can help you solve a problem you were stuck on. Also a chance to say hi to the local crows who appear to recognize me nowadays and don’t fly away when I walk by :)

I work from home, but I do not count my showers as working hours. That’s patently ludicrous, and frankly, 2.5-3.5 hours of “presence” a day is unbelievable. Someone putting in so few hours is shirking their work, period.

My work is in software verification, so it’s not as if I don’t need time to think, but I also put in the actual hours required every day to appreciably kick the can forward.

I’d be livid to be stuck working with (and waiting on) someone who considered their shower and commute as working hours.

The whole concept of salaried roles is that you're being paid to achieve enough to keep your employer happy. If my boss feels like he's getting his money's worth based on my output, it really shouldn't be anybody's business whether I'm achieving that in 3 hours or 12 hours. In fact, if I can produce a satisfactory work output in 3 hours versus somebody else's 8, then I'm not shirking at all, I'm simply better at my job.

And as a knowledge worker, I'm being paid to solve problems, and have and structure the knowledge to solve problems in the future. If I'm solving problems for work in the shower, or on my way to lunch, or while making coffee in the morning, I'm literally being paid to do my job. As a software developer not responsible for operations, literally nothing in my job can't wait 30 minutes. Even if I was at my computer, actively coding, it would probably take around that long for me to get to an appropriate stopping point to respond to a message.

Some people at a previous job used vscode, passed their day clicking at stuff with their mouse, navigating directories via a native file explorer, using GUIs to commit their changes, using windows with no knowledge related to virtual desktop management, automating nothing etc... That wasn't no problem at all : they did their job and at the end of the day they wrote code. But then, with the right tools you could have done what they did in half the time, minimizing all the unnecessary micro-movements with some keybindings and some editor plugins or some really good text editor. Now, if paired with this mechanical mastery you have a good ability to pack related problems/functionalities to implement and are efficient at solving them/implementing them; then you can add some multiplier to the mechanical speed explained in the previous paragraph. That's some weird way to think about this, but let's say the ideal instance of the project requires X lines of code; if you work faster, then you reach a higher level of expertise on the project codebase and by this excess of expertise you gain speed relatively to others which in turn makes you more expert and so on. Except, working "fullspeed" is more tiring than working "normally" and you usually don't want to have a tornado in your team that write 50+ -major changes- commits a day and that cannot cooperate with others because they cannot follow up and are "too slow" to even review those changes. You decide to fire "slow" workers, but then the tornado must work 9+ hours a day to keep up with your expectations and finally burn-out leaving a work that every other member of the team fails to understand, due to too much litterature to read written by some sort of alien. So I'm fine with programming 2 to 4 hours a day, since, as an alien-tornado, I prefer my code to be read, reviewed, and understood by my peers.

Some of us are good at our jobs, use our tools well, and work for the hours we’re paid to work.

You’re not a 10x “alien tornado”, you’re just a fish in a very, very, very tiny pond.

What I am saying is that this conception of work is absurd. The truth is you are hired to build stuff, not for being at an office during X time. I like fishes, that's cute.

I’m hired to spend the time I’ve been paid for building stuff.

If I only dedicate 2.5 hours every day to my work, I’m not meeting that obligation.

If I start accounting for my showers and commute as working hours, I’m being dishonest with both myself and my employer.

Working 2.5 hours per day is enough for me some days to meet expectations. If the person you work for is happy about your output, then should you care ?

If you’re okay working to such low expectations, and do not fear being replaced by automation, then that’s your prerogative.

I would not feel secure in the stability of such an easy job, nor proud of my accomplishments. I also expect that we work in very different stratums in both skill and renumeration.

Somebody got a case of the Mondays!