$ ./new-dimension --present
[init] loading context...
[init] scanning environment...
[init] audience: engineering + product
[init] runtime: 30 min
[████████████████████████████████████] 100%
THE NEW DIMENSION
what changed — and what it means for us
press [SPACE] to begin
You got promoted.
Every person in this room.
You're not coders anymore.
You're engineers. Architects. Leaders.
And your team just got a lot bigger.
$ cat /history/constraints.log
For 50 years, software had one constraint:
Humans write code.
Better languages. Better frameworks. Better IDEs.
All optimizing around the same bottleneck.
That constraint is gone.
AI didn't make coding faster.
It made coding a commodity.
Things that didn't make business sense — now they do.
Things you'd never staff — now they're free.
Tools you'd never build — now they take days.
$ spectrum --describe
MANUAL — you write the code. AI helps with research, questions, boilerplate.
AI-ASSISTED — AI writes code in your project. you review every change. faster, but you're still the bottleneck.
COMPOUND — rules, skills, memory, verification hooks. the system improves itself. each task makes the next one easier.
AUTONOMOUS — defined workflows run without you. verification, deployment, monitoring — automatic.
not a maturity model. a map. no judgment — just position.
$ spectrum --stats
The industry is moving right.
84% of developers use or plan to use AI tools
41% of all code is now AI-generated
4% of GitHub commits are from Claude Code alone
projected: 20% by end of 2026
most teams are at AI-ASSISTED. the unlock is COMPOUND.
Where are you on this spectrum today?
Where do you want to be in 6 months?
Most teams adopted AI to move faster.
Then added human review on every output.
They didn't eliminate work.
They moved the bottleneck.
writing code → reviewing code someone else wrote
Except that "someone" is tireless. And produces at machine speed.
stop thinking:
"AI assistant I supervise"
start thinking:
"engineer I lead"
Set direction. Design verification. Review where it matters.
The code? That's your team's job now.
Three things. The AI handles everything else.
01 DIRECTION
What to build and why. Strategy, tradeoffs, priorities. Where taste matters.
02 VERIFICATION DESIGN
Design the systems that verify code. Don't be the verification system.
03 SYSTEM IMPROVEMENT
When something breaks, fix the system. Not the output.
$ ls ./built-with-ai/
three things I built solo — that only exist because AI changed what's possible
Think about your current project.
What would you build if staffing were free?
What process would you add if it cost nothing?
Not a junior dev to babysit.
A counterpart. An impact magnifier.
$ diff approaches
- micromanaging
"write me a function that validates email addresses"
+ leading
"here's what we need. here are the constraints.
here's how we'll verify it. build it."
The real unlock isn't speed.
It's compounding.
every bug fix → a rule
every pattern → a skill
every preference → memory
each unit of work makes the next one easier.
half your time: shipping. half: improving the system.
feels slow at first. compounds by week three.
$ curl --silent signals.dev/2026 | head
This isn't experimental.
Two challenges. One week.
at work — pick one workflow you repeat. encode it. teach the system. stop doing it manually.
at home — find something that wasn't possible before. build it.
my example: a storybook factory for my daughter.
a few words about her day → personalized chapter → read aloud at bedtime.
not "write stories faster." something that didn't exist before.
That's the new dimension.
bring both back next week.
$ open discussion
Let's talk.