> We pay huge communication/synchronization costs to eek out mild speed ups on projects by adding teams of people.

I am surprised at how little this is discussed and how little urgency there is in fixing this if you still want teams to be as useful in the future.

Your standard agile ceremonies were always kind of silly, but it can now take more time to groom work than to do it. I can plausibly spend more time scoring and scoping work (especially trivial work) than doing the work.

It's always been like that. Waterfall development was worse and that's why the Agilists invented Agile.

YOLOing code into a huge pile at top speed is always faster than any other workflow at first.

The thing is, a gigantic YOLO'd code pile (fake it till you make it mode) used to be an asset as well as a liability. These days, the code pile is essentially free - anyone with some AI tools can shit out MSLoCs of code now. So it's only barely an asset, but the complexity of longer term maintenance is superlinear in code volume so the liability is larger.