Management Blueprint

The episode contains a handful of genuine practitioner observations - org-chart collapse at the manager layer, code production outpacing client absorption capacity, systems-thinkers as the new scarce resource - but roughly half the runtime is generic AI commentary, anecdotes, and meandering tangents that dilute the useful ideas.

“by the middle of 2025, the AI tools for software engineering were as good or better than 50% of the human developers that we employed”

“we get clients saying hey you guys are, you're producing too much. We can't check everything... we can't take another know load of features and capabilities this week”

There are a couple of genuinely contrarian framings - recruiting 'failed entrepreneurs' as systems thinkers, and the argument that middle-management reporting chains are now structurally useless - but the bulk of the conversation recycles widely circulating AI-disruption narratives without adding first-principles analysis.

“maybe we should go look for failed entrepreneurs, which is kind of A heretical thing to say”

“the managers who don't actually produce any output, supervising other managers and compiling the weekly report of reports. It just isn't a valuable job function at the best of times. And now it's useless”

Charles Fry is a genuine practitioner who actually executed a painful pivot - exiting mid-level performers from a ~100-person dev shop and rebuilding as an agentic-first operation - which gives his claims operational credibility; he is not a famous executive but he has done the thing he is describing.

“we were at a hundred people or so, a lot of human turmoil. Our clients were going through the same thing”

“I've actually led three different Salesforce deployments back when I was a CIO cto”

A few concrete data points appear - the 50% developer displacement claim, the $1.8B two-person company from the NYT, a client with 'couple hundred million dollars in revenue' - but most supporting evidence is anecdotal and secondhand, and no client outcomes, timelines, or cost figures are given.

“a guy Not a tech guy, marketing guy. He and his brother run a company, an online company that generates $1.8 billion a year in sales. And it's the two of them”

“we have a client that principally they make pumps and motors... they wanted those pumps and motors to be connected to a network”

The host surfaces a couple of interesting reframes - the product-to-service-and-back cycle, the amoeba org chart - but never challenges a claim, requests a specific number, or pushes back on vague assertions; the conversation stays friendly and promotional throughout.

“it's almost like it went full circle. You had all these product businesses that wanted to become service businesses to create recurrent revenue and now the service businesses... want to become product businesses”

“what are the right kind of customers and right kind of projects for code exitus that would be interesting uh, to look at”