Line of inquiry
Inquiring lines›How does AI reshape human institut…›How does AI adoption affect labor…›this line of inquiry
Do AI coding tools measurably improve developer productivity and code quality?
A broader line of inquiry — a family of 40 specific questions the research asks around this. Follow one into its inquiring-line page, or move sideways to a related line below.
Questions in this line of inquiry 40
Specific inquiring lines the field asks around this — ordered from the most general framing down to the most specific angle.
- Why do experienced developers benefit more from AI coding assistance?
- Does AI coding assistance help junior developers close skill gaps?
- Does AI-assisted coding actually speed up experienced developers?
- Do AI coding tools improve code quality alongside task speed?
- Does AI help more on small greenfield projects than mature codebases?
- Why do developer self-reports of AI speedups tend to be unreliable?
- Does high-level design work benefit differently from AI than routine coding tasks?
- Why does AI code generation lag behind pattern-matching benchmarks?
- Why do novice engineers lose confidence in coding after using AI tools?
- Does minimal code engagement during vibe coding harm students' long-term programming comprehension?
- What self-regulation practices do junior developers use when deciding to accept AI output?
- Why did programmer headcount not shrink after AI coding tools arrived?
- Why do experienced developers report slower task completion with AI assistance?
- What role should code review play in junior developer learning with AI?
- Does prior IDE tool use predict stickiness with new coding assistants?
- Why do low-adoption countries use AI primarily for coding tasks?
- Why do workers who debug most with AI show the lowest learning outcomes?
- How much time do developers spend verifying AI-generated code?
- Why does evaluation of novel primitives require waiting for future reuse to show value?
- Why did developers and experts forecast such large AI productivity gains?
- Why do novices accept AI output without validation in vibe coding workflows?
- How does validating code differ from writing code as a learning mechanism?
- Can AI design tools like Figma Make show speedups when coding tools show slowdowns?
- What role did API access and coding tools play in the output surge?
- What makes intermediate primitives matter more than final code execution success?
- When do students feel authentic ownership of code they co-created with AI?
- Why haven't AI agents replaced human code review workflows?
- How do non-experts evaluate AI-generated outputs when they lack implementation expertise?
- How much time do developers spend reviewing and fixing AI code?
- Why do bug fixes carry more weight than hyperparameter tuning in pipelines?
- Why do recruiters reward AI skills differently across graphic design versus software engineering?
- What distinguishes improvised spreadsheet workflows from institutionalized enterprise software?
- What debugging behaviors signal that a user has abandoned the coding loop?
- Why do some students restart entire projects instead of debugging incrementally?
- How did the junior development pathway work before it became unprotected?
- Why does embedding research tools in coding assistants improve reliability?
- What makes consistency across code, tables, figures, and prose the hard part?
- How does prior coding experience change the way students use vibe coding tools?
- How do skill libraries from human resources compare to hand-written skill libraries?
- How much build time does declarative configuration save versus custom code?