Evolving the Enterprise

The episode covers meaningful ground on the convergence of low-code, vibe coding, and LLM-assisted development, with substantive points about visual programming's role and the difference between specification and programming. However, much of the discussion stays at the conceptual/philosophical level rather than delivering novel, actionable insights. The repeated theme that 'this is just evolution, not replacement' is established early and circled rather than deepened.

“visual programming interfaces utilize tens or hundreds of thousands of years of evolution of the human eye and brain to be able to have cognition of shapes and patterns”

“we are not even with these assistants programming in natural language. We're using natural language as a means by which we can specify our output”

While the hosts make valid points about convergence and collaboration, the core arguments (low-code isn't dying, tools are expanding, this happened before with COBOL/SQL) are well-trodden in tech discourse. The framing of vibe coding as specification rather than true programming echoes Dijkstra's known critique. The reference to Brooks's Mythical Man-Month reinforces established wisdom rather than introducing novel thinking.

“COBOL was supposed to get rid of programming and let business people do the programming. SQL was for business people, not programmers. And we've seen this cycle over and over”

“I love the Dykstra essay on the foolishness of natural language programming”

Jeremiah Stone is CTO at SnapLogic with a demonstrated technical background (NCSA, SAP, data science, multiple languages). He speaks with genuine practitioner credibility and shows serious thinking about systems, architecture, and the long-term craft of software. However, both speakers are internal to the same company discussing their own product space, which limits independence and external validation of claims.

“my entire journey as a technologist started with the mind blowing experience of first writing code. I started with C and wrote some assembler actually I put assembler into production and then I wrote a ton of perl working at the national center for Atmospheric Research back in the late 90s”

“we've done quite a bit of research and are continuing to prototype how we might support a broader community”

The episode lacks concrete examples, numbers, and data to ground its claims. References to Airtable and Pyspark are mentioned but not detailed. The single concrete finding offered - that 'describe this pipeline' was the most-used SnapGPT prompt in 2025 - is interesting but underdeveloped and unsourced. Most arguments remain abstract and illustrative rather than evidential.

“we did a survey of the most used SnapGPT prompt in 2025...the most used prompt, in fact in 2025 was describe this pipeline”

“the team over at Airtable does something extremely similar. When you're building a UI or you're building a crud, uh, gui, they're actually using language models to assemble pre built components”

The hosts engage with ideas genuinely and build on each other's points rather than talking past. Jeremiah raises substantive follow-ups (collaboration drift, interoperability, Conway's Law). However, the conversation stays largely affirmative and exploratory rather than genuinely challenging. Few hard pushbacks or questions that force uncomfortable specificity. The tone is collegial but lacks the tension that surfaces deeper disagreements.

“And I think this underscores the value of natural language and natural language descriptions, both as input in the form of specifications and as output in the form of documentation”

“But worse, you get drift, you get individual drift within your architecture, you get drift within your understanding of the requirements”