Article 004: The IDE as an intervention surface
Key Message: The IDE shifts from “where work happens” to “where decisions are corrected and finalised”.
Series: A — Noticing the shift (Part 4 of 5) Publish Date: Monday 2026-02-09
Story Outline
Opening hook
- IDE = where creation happens (always has been)
- You open file, type → code appears line by line
- Immediate, tactile, visible — you’re there when it happens
- IDE as workbench/studio: not just where you view work, where you make it
- So fundamental it feels definitional
- But: something shifting — not what IDE can do, but what it’s for
The shift
- Still open IDE daily, still write code
- But increasingly: code you’re looking at ≠ code you just wrote
- Agent worked overnight / colleague pushed / refactoring ran
- Work happened without you → now you decide: keep or change?
- Primary action shifts: writing → reviewing, generating → deciding, making → approving/redirecting
- IDE becomes intervention surface — where you step in, assess, steer
- Not where everything originates
Evidence / Examples
Agent-generated PR:
- Open PR created overnight by agent
- Substantial diff — your job: decide if right, not write it
- Scan patterns, check alignment, look for edge cases
- You intervene (comment/tweak/reject), don’t author from scratch
Mid-feature design adjustment:
- Old rhythm: stop, rethink, delete, start again (all in editor)
- New rhythm: describe to agent, let it propagate → return to verify, not implement
- IDE = checkpoint, not workshop
Build failure:
- Open IDE, inspect logs, fix issue in code you didn’t write
- IDE open minutes not hours — intervene and leave
Debugging unfamiliar code:
- Bug in file/system you didn’t build (tool/agent/teammate created it)
- IDE = where you investigate, diagnose, correct
- Reactive not generative
Implications
Tooling evolution:
- Today’s IDEs optimized for authoring (autocomplete, syntax highlighting)
- If spending more time reviewing, different tools matter:
- Diff views critical
- Context summaries (“where did this come from?“)
- New ways of visualising change & relationships within and between projects becomes extremely important
- Navigation: “why changed?” as important as “where used?”
Relationship to codebase:
- Used to: write most yourself → hold in head
- Now: code arrives from elsewhere → can’t hold it all
- More reliant on tools to reconstruct context
- IDE shifts: canvas → lens (look through to understand)
Skills shift:
- Writing well: still matters
- Reviewing well: matters more
- Assess large diffs quickly? Spot misalignments? Know what to scrutinize vs trust?
- Code review skills: occasional → constant
Working vs supervising blurs:
- Shift resembles coding → management transition (familiar)
- But key difference is temporal:
- Speed: decisions needed in minutes, not days
- Volume: much higher rate of change to process
- Cognitive load: less thinking time between decisions
- Hour reviewing agent changes, correcting, approving
- Productive/valuable — but feels different from hour building from scratch
- IDE open either way, posture different
- Not just what changes (supervisory work), but pace and density of supervisory decisions
Close
- IDE hasn’t stopped being central — still where you go when work needs attention
- Nature of attention changing: intervening > originating, reviewing > drafting, deciding > doing
- Not a loss — intervention is still creation
- Different rhythm, different posture
- Workshop becoming checkpoint — both matter, both need skill, not the same thing
Notes
Target: 1,500–2,000 words Tone: Observational, patient, grounded Avoids: Replacement framing, inevitability, hype Builds on: 001 (desktop less central), 002 (work continues without you), 003 (async loop) Sets up: 005 (faster feedback not whole story)