The Cynical Developer

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.

“Psychological safety” has quietly become a synonym for “being nice”, and in this episode we explain why that’s a problem. We look at what it really means, why the healthiest teams disagree more rather than less, why a quiet team isn’t necessarily a safe one, and what actually builds the kind of trust where bad news arrives early instead of late.

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.