The Dark Arts of Software Engineering Team Optimization · Kyle Johnson, Franz Aliquo

AI Team Building for CTOs to Redefine Developer Roles and Hiring in 2026 with Ry Walker

February 13, 2026·46 min·1 clip
College won't prepare you for AI agent development—just like it wouldn't prepare you for the internet in 1992.
Rye Walker sits down with Frams Aliquo and Kyle Johnson to talk about AI agent development and how it is reshaping software teams. He starts from a blunt place: students entering college today who are interested in AI agent development are in for a rude awakening, and he frames it as a dilemma similar to the one technologists faced during the internet revolution. That is the setup. From there, the conversation turns to the practical side of managing teams that build with AI. Walker argues that the real shift is less about creating code and more about reviewing it, because AI can already handle more of the first pass. He says even a small pocket of resistance inside a team can slow AI adoption more than people expect. The point is hard to miss. The hosts then press on hiring and team shape, asking what engineers get wrong about using AI effectively. Walker pushes back on all-or-nothing thinking and treats AI as something to integrate, not worship or ban. He also compares the current moment to earlier technology shifts, especially the internet era that shaped his own path. That comparison is not nostalgia. It is a way of saying that each platform shift forces people to relearn what good work looks like. The discussion also moves into offshore development and whether AI will flatten language and geography as barriers. Walker thinks it may, and he points out that AI-generated summaries, translation tools, and AI-assisted communication can make collaboration feel much more level. That is a real shift. He extends the thought to pull requests, requirements, and the way teams explain work to one another. In his view, if AI can summarize changes cleanly, developers do not have to rely as much on polished natural-language writing to be understood. The episode closes on Tembo and on the year ahead. Walker talks about staying productive in 2026, competing hard in a crowded space, and continuing to learn fast. The conversation leaves with a simple operating idea: AI is already changing who writes, who reviews, and who keeps a team moving.

As heard by us

AI changes team building: less code writing, more code judging, adoption discipline, and better cross-language collaboration.

Rye Walker treats AI team building as an operating problem, not a hype story: once code can be drafted by machines, the harder question is who evaluates it and how adoption changes when the work shifts.

Read the full review in PlayNext →

Why you'd press play

You need a sharper way to evaluate engineers when AI shifts work from creating code to judging it.

Read the full recommendation in PlayNext →
Listen to the show on