Concept

Code Review vs Writing Shift

How AI tools change developer work from primarily writing code to primarily reviewing AI-generated code

Preparing graph…
100%
Concept

Code Review vs Writing Shift

3 visible of 4 connections

Concept

Code Review vs Writing Shift

Description

How AI tools change developer work from primarily writing code to primarily reviewing AI-generated code

Relationships in this graph

Connections

2 Episodes
1 Related Concepts
5 Frameworks
14 Practices

Related Concepts

Ask about this concept

Choose a question to edit in chat.

Which concepts connect to Code Review vs Writing Shift, and why?Which podcast guests discuss Code Review vs Writing Shift? Give examples.How can I apply Code Review vs Writing Shift? Use examples from the podcast.

Transcript Mentions

Well, there are lots of different ways to talk about DevEx. One way to talk about it is kind of three key things that have components that are important of themselves, and they also kind of reinforce each other. Flow state is one of them, cognitive load is another, and then feedback loops are another. I think when you touch on this... Your question about flow state is a really good one, and I'll admit we're just a few years into this. We're still figuring out what the best flow state and cognitive requirements are for people in this because, to your point, sometimes we're getting interrupted all the time. You don't just get in the flow and lock down, and write a whole bunch of code and do the typing of a whole bunch of code as much anymore. Instead, you're kind of creating a prompt, getting some code back and reviewing the code, trying to integrate what's happening in the system, and that can really interrupt.

Nicole ForsgrenSource summary

Source summary: Reviewing consumes more development time.

Browse concepts and frameworks

Nodes in this graph

Relationships

  • How to measure AI developer productivity in 2025 | Nicole Forsgren · discusses · Code Review vs Writing Shift
  • How to measure and improve developer productivity | Nicole Forsgren (Microsoft Research, GitHub, Google) · discusses · Code Review vs Writing Shift
  • AI-Enabled Development · relates to · Code Review vs Writing Shift
  • How to measure AI developer productivity in 2025 | Nicole Forsgren · features · Nicole Forsgren
  • How to measure and improve developer productivity | Nicole Forsgren (Microsoft Research, GitHub, Google) · features · Nicole Forsgren
  • How to measure and improve developer productivity | Nicole Forsgren (Microsoft Research, GitHub, Google) · references · Good Strategy Bad Strategy
  • How to measure AI developer productivity in 2025 | Nicole Forsgren · references · Accelerate
  • How to measure and improve developer productivity | Nicole Forsgren (Microsoft Research, GitHub, Google) · references · Accelerate
  • How to measure AI developer productivity in 2025 | Nicole Forsgren · mentions framework · DORA
  • How to measure and improve developer productivity | Nicole Forsgren (Microsoft Research, GitHub, Google) · mentions framework · DORA
  • How to measure AI developer productivity in 2025 | Nicole Forsgren · mentions framework · SPACE

Source mentions

Podcast excerpts and source summaries from the explorer. Entries marked “Source summary” are summaries, not transcript quotations.

How to measure AI developer productivity in 2025 | Nicole Forsgren

Nicole Forsgren · 00:09:07

Well, there are lots of different ways to talk about DevEx. One way to talk about it is kind of three key things that have components that are important of themselves, and they also kind of reinforce each other. Flow state is one of them, cognitive load is another, and then feedback loops are another. I think when you touch on this... Your question about flow state is a really good one, and I'll admit we're just a few years into this. We're still figuring out what the best flow state and cognitive requirements are for people in this because, to your point, sometimes we're getting interrupted all the time. You don't just get in the flow and lock down, and write a whole bunch of code and do the typing of a whole bunch of code as much anymore. Instead, you're kind of creating a prompt, getting some code back and reviewing the code, trying to integrate what's happening in the system, and that can really interrupt.