It is indeed how you define work. You can quibble if it has to be fully focused producing assets, back to back meetings or just thinking about work related stuf

It is indeed how you define work. You can quibble if it has to be fully focused producing assets, back to back meetings or just thinking about work related stuff, but let’s take a simple one; what I get paid for on paper. I would say, if my pay slip says I worked 80*4 hours then I did. Meals are almost always work really; we sit together and talk code; I also think, at least where I live, breaks like meals are included in your contract as paid time, so I consider them work no matter what we talk/think about. I think a different view is; many of my none-IT acquaintances ‘work’ (in the definition you are looking at) maybe 1 hour a day, and get paid for 32-36 hours (never any overtime, ever, just exactly their contractual hours). But they would say they work 5-6 hours a day. They think I am crazy for working 8+. Realistically, focused asset creating hours, I do 3-5 hours (usually early in the morning), but I easily spend 5 hours just chatting with my colleagues helping them and they me. Doesn’t burn me out for the past 30 years; it would do if I was forced 8 hour focused asset producing.