Service for citizenship, stationed along the border walls and manning really big fucking guns seems to be the place my brain always goes to in these sorts of conversations.
Through circumstance I went from a fully remote working arrangement to working for a place that's 5 miles down a single surface street from where I live (which, during commute hours pushes up to 15 minutes). I go in twice a week, but since we have kids it's mostly a wash. I still vastly prefer the 3 days per week that I work from home. The office gets very busy and very loud, especially in the afternoons.
My employer very successfully shipped a lot of brand new stuff during COVID when everyone was full-time remote. We made a lot of money off of those products. Then they sort of bragged about it. Then they instituted RTO. Now (I'm told, I'm at a megacorp so I'm far removed from these discussions) the executive team is bitching that we're not in office 5 days per week.
I think that's the question - did RTO increase productivity? I haven't seen any audited economic evidence that actually happened. Same as AI - I've seen a lot of PR and hype, but no audited company financials indicators.
Historically though, the data suggests that mass layoffs have a huge impact (negatively) on productivity after a short term "boost" by the survivors.
What's the basis for this war in Iran? Did that stop this administration? This is akin to pointing out that it's actually illegal to drive 30 mph over the speed limit.
How much more productive are we supposed to be in engineering? Are we 10x'ing our testing capability at the same time? QA is already a massive bottleneck at my $DAYJOB. I'm not sure what benefits the company at-large derives from having the typing machine type faster.
Perhaps this is one of the understanding gaps that crop up around AI development? At my current company and most others I've worked at, testing capability is part of the same bucket because engineers do their own QA.
I don't think you can credit Thiel with smelling smoke, he lit the fire. He heard the same statements from SVB leadership about the problems with T-bills and higher fed rates, realized that there was a huge spread between current market value and long market value of SVBs T-bills, and threw a match on it.
Having 1 place (or just generally limiting them) that does the things keeps the dry_run check from polluting the entire codebase. I maintain a lot of CLI tooling that's run by headless VMs in automation pipelines and we do this with basically every single tool.
reply