My tests were describing the code, not checking it

<p>A test proves your code does what you meant. It cannot prove that what you meant was correct.</p> <p>I could have written that sentence a year ago. I still shipped on the wrong

<p>An AI coding agent implements a feature, generates tests, runs them, and opens a pull request with a green build.</p> <p>That looks like independent verification. It often is

<h2> The Asymmetry of Change: Why Your Tests Are Looking the Wrong Way </h2> <p>A passing build is often treated as a certificate of correctness. In reality, it's a narrow

<p>i maintain a powershell script that strips a pile of telemetry and bloat services off a fresh windows install. the feature people actually care about isn't the cleanup, it's

<p>92% code coverage. No SonarQube criticals. All green. And an AI-generated deduplication bug made it to production because not a single test had challenged the logic.</p>

<p>Last month I asked a senior candidate the same question I ask everyone. "Tell me about a flaky test you fixed and how you fixed it."</p> <p>She paused and said, "I just added a

<p>The more I use AI tools like Claude Code, the clearer it becomes: engineering skills are what make AI output worth shipping.</p> <p>AI makes writing code faster. But shipping

<h1> My Exit Rule Said '2 Periods' — My Code Was Counting Something Else Entirely </h1> <p>My funding-rate bot has an exit rule that reads like plain English:<br /> </p> <div