The rules were written down. Nobody followed them. Then CI went red on day one

<h1> Production Was Down… But Everything Looked Normal 🤯 </h1> <blockquote> <p>A real debugging story about silent failures and why thinking matters more than tools.</p>

<p><strong>Both rules were well written. They contradicted each other and I hadn't noticed, because writing a rule and making a decision are not the same job.</strong></p> <p>I

<p>A teammate deleted a test file on a Friday. Not on purpose. The suite still passed. The pipeline still went green. Nobody noticed for three weeks.</p> <p>Here's the part that

<p><em>This is my entry for DEV's Summer Bug Smash — Smash Stories.</em></p> <p>Not every good bug is an epic. Some of them are one character long, and the interesting part is

<p>Two posts ago I said I'd shipped code I never read. It's easy to write that as a general observation about the industry. It's less comfortable to go open your own repo and

<p><em>This article was originally published on <a href="https://etherealogic.ai/exit-code-2-how-claude-hooks-turn-agentic-rules-into-runtime-barriers/" rel="noopener

<p>I have a scanner that grades my own projects. It reads the code, applies a list of rules, subtracts points per finding, and hands each project a letter grade. It exists because