Every episode of the Cynical Developer podcast

The whiteboard puzzle always tested the one mode the job never uses — alone, from memory, no help. We look at why AI finally makes that impossible to ignore, why hiring clings to it anyway, and what’s worth measuring instead.

We argue prompt engineering is already on its way out — and what’s replacing it is one of the oldest skills in software. When generating code gets cheap, deciding precisely what to build becomes the whole game.

A quiet split is forming in software teams — not junior versus senior, but developers who’ve learned to work with AI and those who’ve decided not to. We look at what the divide really is, why it compounds, and why plenty of brilliant people are on the wrong side of it.

We dig into the gap between responsibility and ownership — why so many teams are accountable for outcomes they were never given the authority to control, and how “you own this” quietly becomes “you hold the pager”.

We take on the tidy story that remote work killed productivity. It didn’t — it removed the things that were hiding weak management. We look at the presence trap, what genuinely broke, and why the easy diagnosis pointed at the wrong people.

We look at a cost that never shows up on any report: the wreckage an interruption leaves behind. Not the thirty-second question, but the twenty-minute rebuild — and why unpredictability, not volume, is what really destroys deep work.

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.