Code Review Live

Code Review Live is what happens when three working engineers open a real production codebase together and react in real time. Every episode picks one open-source project or one anonymized closed-source module and walks through it: the decisions that aged well, the decisions that didn't, and the recurring pattern of mid-career engineers protecting choices they made under deadline pressure five years ago. Recurring formats include "Defend Your Stack" (one host argues for a specific architectural choice while the others stress-test it), "Refactor In One Hour" (what a panel of three would actually change if given sixty minutes), and "What This Service Was Going To Be" (post-mortem reads of high-profile sunset projects). For working engineers who learn more from real code than from clean tutorials.

1. 01

   We Read All of HN's Source Code

   Three engineers spend ninety minutes inside the actual Hacker News codebase. The defense of Common Lisp is more interesting than you'd think.

2. 02

   Defend Your ORM

   One host has used Prisma in production for four years and is going to argue with the other two about every choice.

3. 03

   Refactor This Auth Service In One Hour

   Anonymized auth service from a well-known SaaS — the panel rewrites the riskiest module in an hour, defending every cut.

4. 04

   The Microservices We Regretted

   Three engineers walk through services they personally architected and would now collapse back into monoliths.

5. 05

   Reading Linear's Sync Engine

   An hour with the open-source parts of Linear's offline-first sync, and the trade-offs that show up only at scale.

6. 06

   What This Service Was Going To Be: Google Reader

   The post-mortem read on the codebase Google killed — what was over-built, what was under-built, and the lesson that still matters.

7. 07

   The Build System We Should Have Had

   An honest read of three real CI/CD setups — and the one architectural choice that would have prevented the worst on-call incident in each.

8. 08

   How NextJS Got So Big

   An engineer-level read of the design choices that made the framework win, the ones that aged into liability, and the parts the team wishes they could redo.

9. 09

   Production Postgres Schemas, Roasted

   Three engineers receive three real production schemas in advance and walk through them on air — the defense from each schema's author is the best part.

10. 10

    Refactor Your On-Call Rotation

    Less code, more humans. The panel reads three real on-call playbooks and identifies the structural changes that would have prevented the last bad incident in each.

• 01

  “Three engineers, one production codebase, zero preparation. The defense of the architecture starts in the next sixty seconds and gets worse from there.”

• 02

  “The choice we're about to roast for the next ninety minutes was made in a single afternoon, under a deadline, by a person who has since left the company. Be kind.”

• 03

  “Today's codebase has been live for fourteen years. We are not going to be kind.”

• 04

  “The author of the code we're reading today is on the call. They have requested anonymity. Let's see how long they hold out before they unmute.”

• 05

  “By the end of this episode you will have one architectural opinion you didn't have at the start. We make no promises about which direction.”