there's no behind

i used to keep a running tally of how behind i was. behind the kid who started coding at twelve. behind the person who already shipped the thing i'm still planning. the tally was always growing, and it never once helped me write a line of code.

the reframe that actually worked: stop measuring against the calendar and start measuring against proof. i'm not behind because of what month it is. i'm either able to do the thing, from a blank file, or i'm not yet. that's the only status that exists.

there's no behind. there's only gate cleared, or gate not cleared yet.

a gate has a hard, objective pass condition. rebuild it from scratch. ship it with no leaks. explain it to someone with no context. when i hold myself to that, comparison loses its grip, because the only person on the other side of the gate is me.

the slow truth underneath this is that everyone's progress looks obvious in hindsight and felt like fog while it happened. i got into that in the obscurity of greatness. and the way you keep clearing gates without flaming out is its own discipline, which is the pace that survives.