Building StareBrain — say a command in plain English, see exactly what it's about to do, confirm before anything runs. Got called out today in a way that's sticking with me. I'd concluded my data schema keeps a value and its provenance tag together — reasoned through it, felt confident, moved on. Someone pointed out that reasoning about your own schema barely counts as a test, because it's the easiest place for a comfortable answer to hide. You're grading your own homework and calling it verification.
The actual test is almost insultingly simple: take one real entry, push it through whatever code path copies or logs it, print what comes out the other side. Five minutes. Either the tag survives or it doesn't. No amount of confident reasoning substitutes for actually running it.
Haven't run it yet as I write this — which is itself the point. "I'll check it later" is just another version of trusting my own conclusion a little longer. Going to actually do it today and report back whichever way it goes, including if it turns up the exact bug this whole two-week series has been about, in my own code.
Building in public as I go — waitlist link in profile if you want to follow along.