I see where you're coming from. One of the pieces of cognitive dissonance I had at Google was that I always had so much work to do, and there were just so many people around the office chilling out; waiting in long lines for free food, playing ping pong, making themselves an espresso. I never really felt like I had time for that; I got a grab and go sandwich and drip coffee and then hung out at my desk for 8 hours. I started the day with an infinite amount of work, and ended the day with an infinite amount of work. The melancholy of a good idea is that working on it just yields more good ideas; no matter how much work you get done, you'll always be making more.
The downside to my approach is that I super burned out. I had "strongly exceeding expectations" for 2 quarters, then my project was cancelled so I switched teams and went on a PIP. Indeed, I flat up stopped showing up to work. (I was so bitter about the fact that I lined up a new job immediately, but people that didn't do that got 6 months of paid vacation to explore other teams. I got nothing, and I needed it bad. The company doctor did give me antidepressants and some unpaid leave though. Thanks for that, turns out antidepressants don't treat burnout.)
I didn't even know that burnout was a thing back then, but if I did, I would know that making sure that you jam in 40 hours of programming and meetings into every week without taking a break isn't that healthy or productive over the long term. All these people chatting in the lunch line or playing ping pong or doing an aggressive workout and then showering in the middle of the day were optimizing for their long-term productivity. 1 hour less task-doing today, 10 extra years in their career. Not a bad tradeoff at all.
At a startup, you might not be able to afford that; by the time you're burned out, you've already sold your company and are retired, so it's all good. But at a big company, it makes a lot of sense; talent acquisition is expensive and if you can get 10 years out of someone instead of 6 months, you're going to be a lot more successful. And there's that uncomfortable medium where that extreme productivity didn't actually make a business that can afford to not burn people out, but now everyone's burned out. A lot of companies are in that state, and there isn't an easy way out of that without a time machine.
Engineers that call you out on you burning them out are absolutely right to complain. The basketball game is a much better use of their time than the standup. Standups only matter to people organizing the project; the meeting is only for your benefit. It saves you the time of reading their commits and design docs, sitting in on their engineering discussions, soliciting feedback when writing performance reviews, etc. The actual creative work of software engineering is done when your head is free from distractions and anything you don't need to know about. A walk around the quad or a basketball game is a great way to chew on the ideas, discard all that's unnecessary, and set you up for the 4 hours where you physically translate a quarter's worth of thinking into code that can be checked in.
At the end of the day, it's not really the software engineer's fault for the company losing money. Businesses fail because there is not a plan for making money and the actual engineering tasks are irrelevant. "Sprint 12323: rearrange the deck chairs on the Titanic." is what 90% of software engineers are doing right now. They are right to go elsewhere when your business plan is so bad that the company can't even afford blueberries. Do you really think that if people just sat in front of their computer for 30 more minutes a day, or provided better updates in their standup, that the bad idea of a company would be saved? Some companies just weren't meant to be. VCs are very bad at not giving these companies money, though, so there are a lot of people running in circles doing nothing as they slowly realize they never should have started the company. Ultimately, you can't blame the nice campus or intramural basketball league for that.
The downside to my approach is that I super burned out. I had "strongly exceeding expectations" for 2 quarters, then my project was cancelled so I switched teams and went on a PIP. Indeed, I flat up stopped showing up to work. (I was so bitter about the fact that I lined up a new job immediately, but people that didn't do that got 6 months of paid vacation to explore other teams. I got nothing, and I needed it bad. The company doctor did give me antidepressants and some unpaid leave though. Thanks for that, turns out antidepressants don't treat burnout.)
I didn't even know that burnout was a thing back then, but if I did, I would know that making sure that you jam in 40 hours of programming and meetings into every week without taking a break isn't that healthy or productive over the long term. All these people chatting in the lunch line or playing ping pong or doing an aggressive workout and then showering in the middle of the day were optimizing for their long-term productivity. 1 hour less task-doing today, 10 extra years in their career. Not a bad tradeoff at all.
At a startup, you might not be able to afford that; by the time you're burned out, you've already sold your company and are retired, so it's all good. But at a big company, it makes a lot of sense; talent acquisition is expensive and if you can get 10 years out of someone instead of 6 months, you're going to be a lot more successful. And there's that uncomfortable medium where that extreme productivity didn't actually make a business that can afford to not burn people out, but now everyone's burned out. A lot of companies are in that state, and there isn't an easy way out of that without a time machine.
Engineers that call you out on you burning them out are absolutely right to complain. The basketball game is a much better use of their time than the standup. Standups only matter to people organizing the project; the meeting is only for your benefit. It saves you the time of reading their commits and design docs, sitting in on their engineering discussions, soliciting feedback when writing performance reviews, etc. The actual creative work of software engineering is done when your head is free from distractions and anything you don't need to know about. A walk around the quad or a basketball game is a great way to chew on the ideas, discard all that's unnecessary, and set you up for the 4 hours where you physically translate a quarter's worth of thinking into code that can be checked in.
At the end of the day, it's not really the software engineer's fault for the company losing money. Businesses fail because there is not a plan for making money and the actual engineering tasks are irrelevant. "Sprint 12323: rearrange the deck chairs on the Titanic." is what 90% of software engineers are doing right now. They are right to go elsewhere when your business plan is so bad that the company can't even afford blueberries. Do you really think that if people just sat in front of their computer for 30 more minutes a day, or provided better updates in their standup, that the bad idea of a company would be saved? Some companies just weren't meant to be. VCs are very bad at not giving these companies money, though, so there are a lot of people running in circles doing nothing as they slowly realize they never should have started the company. Ultimately, you can't blame the nice campus or intramural basketball league for that.