
The Error Handler That Ate The Errors
I added a safety net to make failed data loads impossible to miss. Then I watched a page fail to load and say nothing at all.
Topic
7 posts on this topic.

I added a safety net to make failed data loads impossible to miss. Then I watched a page fail to load and say nothing at all.

My tool generated a preview website for a real business and it read as generic slop. The fix was not a better prompt. It was encoding my taste somewhere the machine can reach it.

IntoAction runs SQLite in dev and Postgres in prod, with Drizzle promising the two are identical. They are not. The leak showed up in a JSON column that came back parsed on one and raw on the other.

Building workman, my agent orchestration tool, meant detecting cycles in a dependency graph. A good error names the loop; a useless one just says one exists.

Building ContentForge's AI pipeline meant threat-modelling it properly first. Here is the practical, plain-English checklist of twelve places things go wrong, and how to harden each one.

I tore the old WordPress site down to the studs and rebuilt it as a fast, repo-native Astro project on Cloudflare. Here is the why, the how, and what I would do again.

I have more projects on the go than one person has any business running. Here is the system that makes that ambitious instead of insane, and the honest catch in it.
No matches, try another word.