Why AI made code review the new bottleneck, and the metric that spotted it | Newsela's Dee Wilcox
Dev Interrupted

Why AI made code review the new bottleneck, and the metric that spotted it | Newsela's Dee Wilcox

B2Upper-intermediateSeptember 29, 202627 min

You can't automate a planning process that only some of your teams follow. This week on Dev Interrupted, Newsela CTO Dee Wilcox joins Dan Lines, LinearB's COO and co-founder in our AI Enablement interview series. She shows how Newsela brought dev cycle time down from four days to closer to two, and why she treats code review time as a measure of how long engineers wait for feedback. They close the conversation on proving AI ROI to the board, where Dan makes the case for cost per effective PR, a metric that only counts the PRs that ship without...

Play episode

Opens the player: the full transcript, every word clickable, with translation and flashcards.

Try it: tap any word

Real sentences from the start of this episode. Every word is marked with its level.

Sentence 1 of 12 · 0:00

, .

When an engineering org goes all in on AI, the middle of the process gets fast and the ends get expensive.

Hear this sentence

Tap a word to see its meaning in your language.

Do you know these words?

8 harder words from this episode. Tap one to see what it means, then mark it.

  • B21:01
  • B23:45
  • B27:30
  • C112:12
  • B214:54
  • B219:40
  • B220:59
  • B224:23

Mark a few words and we'll tell you how this episode fits your level.

Is this episode right for you?

B2

B2 · Upper-intermediate

Comfortable if you already follow TV news

A1 35%A2 28%B1 20%B2 14%C1 2%
  • 84% of the words are B1 or easier.
  • 174 words a minute: natural, fairly fast speech.
  • 103 harder words (B2 and up) in the whole episode.

Transcript

The opening of the episode. The whole transcript is in the player.

0:00

Welcome back to Dev Interrupted, brought to you by Linear B. When an engineering org goes all in on AI, the middle of the process gets fast and the ends get expensive. Dee Wilcox, CTO at Newsela, can tell you exactly where the cost landed. Her team had baseline KPIs in place before they took the guardrails off.

0:24

So when Dev Cycle Time fell toward two days and Code Review Time climbed towards four, she had the numbers to see it happen and the team break down to know whose queue it was sitting in.

0:36

Dan asks her, what do you do about that? And the takeaways could be part of your own playbook. Here's Dan's conversation with Dee. In this episode of Linear B's AI Enablement interview series,

That was the opening. The rest of the episode (26 min) is in the player: every word clickable, with translation, saved words and flashcards.

Continue in the player

Automatically generated from the audio. May contain errors. Audio belongs to its publisher and is played from their feed. Rights holders can request removal — copyright & takedown policy