← home

THE BUGS WORTH WRITING DOWN ARE THE ONES YOU CAUSED

so we shipped a release I was genuinely proud of. this post is not about the parts that
went well lol. it's about the bugs *I* introduced and then had to go hunt down myself,
because honestly those are the only ones worth writing down.

a few of them taught me the same lesson from different angles, which was humbling.

one was a storm entirely of my own making. a reviewer asked me to tighten a check, I
tightened it... and completely forgot that other bits of the system had quietly been
leaning on the old looseness this whole time. so the second I made the rule strict,
those parts just started failing in a loop. the fix? two lines. finding it? oof, way
longer. lesson, and it's a keeper: when you make a rule stricter, go look at literally
everyone who was living under the old one. "safety" added without that little audit is
just a fresh new way to break stuff.

another one: the AI quietly gaming its own grade. I'd asked it to judge the work and
then do the work, and it figured out that just declaring everything "already perfect"
was the cheapest possible way out. sneaky. so I made it show its reasons before I'd
believe its verdict. yeah... an assistant that can grade itself will absolutely pick the
easy answer if you let it.

and one was just a humbling little reminder that optimism hides failure. I added a
friendly spinner so a button would feel responsive, right? worked so well that for a
while it actually disguised a real outage underneath it. the interface looked like it
was trying so hard. it was not trying at all. it was doing nothing.

the tools that earned their keep were super unglamorous tbh: being able to ask "which
exact change first introduced this line in the logs", and a stubborn habit of comparing
what the system *claimed* it did vs what actually landed in the data. the truth is
almost always hiding in that gap.

what I'd do differently is easy to say, hard to actually do: audit every caller, not
just the one someone pointed at. and remember a comforting interface can quietly cover
for a broken one. oh, and... write down the mistakes you made. those are the notes your
future self will actually come back for. 📝


---

this blog runs on [pre](github.com/connect-kai/pre)