You can go even deeper with this idea. How much of your time coding is actually coding? Surely, you're not typing all the time. If you take 10 minutes to think over a concept and explore some options before writing a block of code, how do you know if that was an appropriate amount of time or if 9 of those minutes were wasted or whether you should have taken much longer than you did? Personally, I have no way of quantifying any of this.
You could say the same for carpentry. Are you working when you're commuting to the job? No? What about when you're at the job, and putting on or removing your personal protective equipment? Or when you're walking to the job site? Or hearing the instructions before you begin? Or looking at the work and thinking what the best way to go about it is? Or when you actually make a to-do list in order? Or when you move around the site? Or when you're not moving, but don't have a hammer in hand? Or when you do have a hammer in hand, but aren't swinging it toward a nail? Or when you are swinging it, but it hasn't hit the nail yet?
I would argue that if the concept of real work shifted enough there would be people who thought only the milliseconds the hammer is pushing a nail through the wood, aggregated throughout the day, is real work. Likewise, you could only count the time the keys are on a rising edge between 0 and 1.
My rule is if you wouldn't do it if you didn't work, and it's necessary for the output of the work, it's work.
