Episodes tagged: Season 2

We pull apart a quiet truth most teams can see but rarely say: the strongest engineer often isn’t the one who gets promoted. We look at why visibility beats impact, why the best work leaves the least evidence, and what both sides can actually do about it.

We pull apart psychological safety and “being nice” — why healthy teams disagree more, not less, and why a quiet team isn’t necessarily a safe one.

Why do performance reviews reward visibility over impact, and why do so many developers leave them feeling misunderstood? In this episode, James unpacks why performance reviews are quietly broken, and what that’s doing to teams.

Developers leave jobs all the time, but rarely share the real reasons. James explores why developers quit and what companies miss.

James takes aim at management practices that are hurting developer productivity and morale. What do managers need to stop doing?

James explores spec-driven development and how it changes the way developers actually work with AI tools to build better software.

AI can help write code, but it can also make your codebase worse. James explores the pitfalls of AI-generated code and how to avoid them.

As AI becomes embedded in software development, ethical questions arise. James discusses the moral considerations teams should be thinking about.

No-code platforms promise to democratize development, but they keep falling short. James examines why no-code struggles to deliver on its promises.