The second axis most maps miss: not how much you hand the model, but how much of your work survives the session as state you can open and inspect. Cleanest articulation of this I have seen.

Mike Czerwinski argues that 'vibe coding' is not a skill level but an axis measuring how much of a developer's work persists as inspectable state after a session. He critiques common maps of AI-assisted coding that focus only on how much code the model generates, missing the critical dimension of state persistence and inspectability.