ai detox

practice

nineteen of them, one at a time. sit with it — or draw again.

一

unmetered

free forever. they show you the territory, not a description of it — that's why they deposit.

$ grep -rn "string from the UI" .      # where the behavior lives
$ git log -S "suspicious line"          # when it appeared, and what the commit said
$ git log --oneline -15 -- path/file    # what this file has been doing lately
> go-to-definition / find-references    # the actual call graph
> breakpoint, then step                 # the real path, not the idealized one

read here, release there

read every line

money
auth & identity
deletion
migrations
external writes
anything that fails silently

no exceptions. the time to read it is part of the cost of generating it — count it in up front, don't defer it.

let it ride

rendering lists
admin scripts
internal one-offs
throwaways

survivable, and it fails fast.

obstacles

first three craft sessions feel awful. that's withdrawal, not decline. it's where people quit.
the lost sediment doesn't come back on demand. distrust any plan that promises it.
part of the old joy was being "the one who could." that version isn't returning. knowing a system deeply still is.

the map was never drawn. nobody is holding it.
the meter is on the wrong resource. the limit resets sunday. the code doesn't.
risk concentrates where the halo is brightest — in the code you couldn't have written.
plans built on vigilance die in week three. build on structure instead.
seniority is deletion. the thing not built, the abstraction refused.