Noah Laphart

To see how active telemetry works in practice, get a demo at mezmo.com slash codestory.

That's M-E-Z-M-O dot com slash codestory.

This episode is sponsored by Unblocked.

There's a good chance you've already tried a few AI code review tools, and you're probably ignoring most of their comments.

Not because AI can't review code, but because it's missing context.

Most AI reviewers focus on surface-level issues, style nits, obvious refactors, or restating what's already clear from the diff.

Meanwhile, the things you actually care about, like whether a change violates an earlier architectural decision or quietly duplicates existing logic, go unnoticed.

That's the problem Unblocked is built to solve.

Unblocked's AI code review is grounded in decision-grade context, prior PRs, design discussions, documentation, and system-level constraints, the same context senior engineers rely on when reviewing code.

Teams using Unblocked report fewer comments, higher signal, and automated reviews they actually trust, enough that many have turned off other review tools entirely.

Even if you've already written off AI code review, Unblocked is worth a look.

Get a free three-week trial at getunblocked.com slash codestory.

That's getunblocked.com slash codestory.

So this will be interesting, my next question around scalability.

And I'm curious where this comes into play.

Where did you have to factor scale into your decision making?

And were there interesting areas where you had to fight it as you grew?

So as you step out on the balcony, look across all that you've built thus far with Chris, what are you most proud of?

Okay, let's flip the script a little bit.

Tell me about a mistake you made and how you and your team responded to it.