It's quite possible for x work + y frustration and self loathing to be x=0 and y=30 as you hope no one notices you coming in late / leaving early and being totally vague about progress during daily meetings. I think those behaviors and 'zoning out' are mostly orthogonal to hours 'worked', though.
There's probably some agreement somewhere. I do think a lot of 80 hour, 100 hour work week boasting is just that, boasting, and surely for some doesn't really translate to that many hours of "real work". It comes from creative accounting of work hours and I think is rooted in a poor work/rest of life separation. Think about your startup for a while during dinner? I guess you're technically working, huh? Or for video game testers, your bugs filed / hour playing the game looking for bugs isn't a nice flat line with a sharp drop off after 8 hours, but a lot of people out of the industry will say "you're just playing a video game over and over for 12+ hours a day for weeks and call that work?".
I believe that's a fallacy. Especially in software you just won't get more work done by working longer hours. Your 60 h week will at best be 40 h work + 20 h zooning out. at worst, it'll be 20 h work + 40 h frustration and self loathing because you can't focus on your work.