The dichotomy being presented here is great, and I appreciate the tact in presenting each side's strengths -- a tasteful and enjoyable read. It _is_ possible after all to exist on either branch of this bifurcation and have respect for the other side, even though (hint hint I'm looking at you, "pure" engineers) such a divide is the root of much intellectually-veiled baiting.

I do not however agree with the author that "pure engineering" is going away:

> But like I said, those times are gone. Tech companies now have to make money.

Tech companies have always had to make money... in a vacuum. The return of an AI hype-train laden with VC cash has in many senses recreated some of the air of extravagance of the 2010s-era; perhaps with even more frivolity than last time. I think the author is mistaking a decline in OSS library and tooling spending by companies -- for human use -- as fall in pure engineering efforts. I'd argue instead that the definition of what counts as a "pure engineering" effort has simply shifted to AI-based tooling. We see now, and will continue to see, lots of high-octane-brain-power effort and money being sunk into building the "best" protocols, interfaces, and libraries to interface with AI... which will also likely be OSS too!

The purist flamewars will just be about a lack of understanding of MCP rather than how to use Rust. :)