Blog
Practical notes on checking code written by people and AI.
Why a check exists, what it measures, how it fits the development workflow, and where its limits are - written by the person who ships Iris Code.
So you're a code copier? What else do you do.
Copy-paste is the only kind of technical debt that feels like productivity while you're creating it - and the only kind you can't grep for after.
Read more
Filter
7 posts
So you're a code copier? What else do you do.
Copy-paste is the only kind of technical debt that feels like productivity while you're creating it - and the only kind you can't grep for after.
Your AI just changed 14 files. Now what?
Code review was designed for pull requests. The work now arrives one prompt at a time.
The year your dependencies started hacking you back
Somewhere between August 2025 and now, "check your dependencies" stopped being good hygiene and became a full-time job nobody was staffed for.
The slopification of software engineering
Nobody decided to lower the bar. The bar just stopped being checked.
Technical debt isn't debt. That's the problem.
Real debt has an interest rate, a due date, and a lender who calls. Technical debt has none of that - which is exactly why it never gets paid.
You're not as smart as you think you are
You didn't skip the linter because you're lazy. You skipped it because some part of you assumed your code was already fine. That assumption is the bug.
Nine security anti-patterns your linter doesn't catch
ESLint catches style problems, not security problems. These nine patterns pass code review, pass CI, and still ship to production. Here's how to spot them before they do.