Vito Carella

One day, we got an email from a user confused as to why our application displayed "Error 403" after trying to invite a teammate. That was all he could tell us. I had written that particular error message almost eight months ago, so I had never even thought about it again since then because I knew what 403 meant.

I decided to go through every single one of the error messages in the product and re-write them to inform the user what had gone wrong and how he could proceed. Support emails about "The app is not working" decreased significantly, despite the bugs in question remaining exactly the same. I knew what the problems were. I just did not see them anymore.

There s no standup, no manager, no deadlines that matter to anyone else. Once, I went three weeks without shipping anything and literally couldn t remember where my days went.

How it got fixed: Two other solo founders and me have a three-line message each Monday. This is what I shipped, this is what I m shipping, and this is where I m stuck. No meetings, no theatrics. We ve been doing it for fourteen months now.

I ve run into this with longer agent runs and I m curious how others handle it.

The original issue might contain the scope, constraints and evidence required. But when another model or session picks up the work later, those conditions often get reduced to a summary.