Earlier quoted context omitted.
Agreed. when I started in the 90s I often got several months of focused work without many interruptions. I did that too. Quite often the project failed after those months because we'd built the wrong thing, or the landscape had changed, or the customer had failed to spec what they needed well enough. This was the "Waterfall" methodology, and Agile, with all its meetings, is specifically designed to fix that problem.
My favorite Agile failure case is when you have all the meetings and still fail, because you spent all your time on Agile paperwork instead of designing and building a product.
Besides, why can't we be lower case agile, and avoid all these meetings anyway? I write very detailed PRs with high level summaries, screenshots and videos, explanation of risks and trade offs, and deeper technical dives. Everything you need to know about what I'm working on is literally right there. I push up code early and often, it's not like I just want to sit in an isolated cave for 6 months and then emerge with a finished product.