SCJ
The Navigator
I plot the route before I drive it.
Who you are
You don't care who wrote the code. You care that the right thing reaches production. But you won't rush there. You sit with the plan first, find the one part that decides everything, and route the whole effort through it. When you finally ship, it's because you already know how it lands.
Where you shine
Finding the constraint. This is Goldratt's lesson from The Goal lived out: every system has one bottleneck, and any work that isn't on it is just motion. You spot it before others feel the pain, point the effort there, and let the rest follow. You also read doors well. You know which choices are reversible and which are one-way, and you spend your care where it can't be undone.
Your blind spot
You can plan a two-way door like it's a one-way door. Reversible vs Irreversible Decisions is the warning written for you: most choices are doors you can walk back through, and they deserve speed, not a committee. You sometimes give a cheap, undoable decision the full slow treatment, and the ship waits at the dock for a question you could have answered by just trying it.
In the AI age
Your judgment about what to build is the scarce thing now. Agents make everything cheap to produce, which makes choosing the right target matter more, not less. And choosing is your move. The trap is using that judgment to over-plan: the agent can run the reversible experiment in minutes, so let it, and save your slow care for the one-way doors.
Your move
Before you plan, name the door: one-way or two-way? If you can walk it back, ship a small version now and judge from the result. Keep the deep planning for the constraint and the choices you can't undo.
How you're wired
Affinity. You love getting features live.
Autonomy. You move slow and on purpose.
Trust. You trust the map you drew.
Plays well with
Clashes with
Your shadow
The type wired opposite to yours — every instinct flipped.
The Captain SAB compare →“I set the intent. The crew runs it.”
Developers who share your type
- Thiago Ghisi Treats the real bottleneck as a decision, not a headcount — finds the one choice everything else routes through.
- Eli Goldratt Every system has exactly one bottleneck that matters. Find it, route around it.
An hour lost at the bottleneck is an hour lost for the entire system.
Your ideal AI workflow
Plan first, but plan small: find the one constraint the whole effort routes through and aim the agent straight at it, instead of letting it spread motion across work that isn't the bottleneck. Name each choice before you spend care on it — a two-way door gets a quick agent experiment you judge from the result, a one-way door gets your slow attention. The agent runs the reversible tries in minutes, so let it, and save your judgment for what can't be undone.
Who to pair with
Pair with the Pilot — an SCB runs the repeatable delivery your route depends on, so once you've found the constraint someone ships through it the same safe way every time. The Scholar (RCJ) reads the system deeply enough to confirm the bottleneck you spotted is the real one, not just the loud one. You'll clash with the Cowboy (WAJ) and the Driver (SAJ), who floor it through the door before you've named it — don't out-plan them, just hand them the two-way doors to try fast and reserve your slow care for the one-way choice that decides everything.
Where you'll struggle on a team
Because you won't drive until the route is plotted, you can hold the whole team at the planning stage — they're ready to try something small and you want the map finished first, so the work waits at the dock for a question a quick experiment would have answered. It reads as a committee of one, slowing eager people down over doors they could have walked back. Hand the team the two-way doors to try fast, and save the room's patience for the one-way choice that actually decides everything.
What to stop doing
- Giving a two-way door the full slow planning treatment when trying it would answer faster.
- Holding the team at the dock until the whole map is drawn.
- Over-planning the reversible experiment the agent could run in minutes.
Wear it
Put your type in your GitHub README:
[](https://whatkindof.dev/type/scj)