DEV PRODUCTIVITY
in the glittering AI future

what we've seen in ? TB of coding agent logs.

Dave Slutzkin - CEO Cadence

2026: Everyone's using AI coding tools.

Three things guide effectiveness and productivity:

Models/Tools

Way too soon to standardise, unfortunately.
Definitely don't use Copilot.

Developer

How you work matters but everyone's working differently. No best practice yet.

Codebase

Legacy code is fine, but docs and tests make a huge difference to the agents.

State-of-the-art this week

codex + gpt-5.4

% of AI coding sessions with successful outcome

Codex
Claude
100% 90% 80% 70% 60% Jan 6 Jan 20 Feb 3 Feb 17 Mar 3 Mar 17 opus-4.6 codex-5.3 gpt-5.4

After
vibe coding

How do we make this engineering?

Three modes of AI coding

Autocomplete

10–20% faster?
Copilot/Cursor hegemony. Broken tab keys.
API compatible with previous workflows.

Vibe coding

10x faster?
Claude Code is the new emperor. Fast, sloppy, liberating. Probably unmaintainable.

Agentic engineering

3x faster?
Autonomous agents guided by real specs, tests, and guardrails. Production quality.

Mind-meld with the agent(s).

PRs per week

Cadence Client #1 Client #2 Client #3

Average hours to merge PR

Cadence Client #1 Client #2 Client #3

Backpressure and docs

Help the agent with the codebase

Where we need to get our legacy code to

Three things to take back to your team

Models/Tools

It changes every few weeks. Right now: codex + gpt-5.4. Don't standardise yet.

Developer

Mind-meld with the agent. Long planning, tests first, small parallel tasks, automated PR review.

Codebase

CI-heavy testing, deep docs with progressive disclosure, harness engineering to unblock agents.

teamcadence.ai

Cadence dashboard

Q&A

Dave Slutzkin

← → navigate