Coming soon · A new book
Everyone runs on code. Most of it works. This book is about the part that doesn't, and what happens when you finally stop ignoring it.
The Premise
A glitch is a small, recurring failure. It doesn't take the system down. It just runs quietly, every day, taxing everything else.
People have glitches too. The decision you keep re-deciding. The project you keep restarting. The story about yourself you wrote twenty years ago and never refactored. None of it crashes your life. All of it costs you.
Scratch Your Glitch treats self-improvement the way a good builder treats a bug report: without drama. You don't need a new you. You need to find the loop, read it honestly, and ship the fix.
"The most expensive bugs are the ones that never throw an error. They just run forever."
This is a book for people who build things: companies, careers, families, teams. People who debug systems for a living but have never once run a diagnostic on themselves.
A Field Guide
You made this decision already. Then you made it again. You will make it once more tonight at 2am. The loop never resolves because resolving it was never the point.
Every past failure stays loaded in working memory. Nothing ever gets released. Eventually there's no room left to run anything new.
Ten projects started, zero finished, all of them competing for the same attention at the same time. Whichever one is loudest wins. None of them ship.
Rules somebody else wrote into you decades ago. Nobody remembers why they exist. You follow them anyway, because removing them feels dangerous.
The habit that never throws an error and never makes a scene. It just skims a little off the top of every single day. You'd fire a vendor for less.
"That's just how I am." A constant that should have been a variable. The single most expensive line in your entire codebase.
Inside the Book
Part One
How to notice the loops you've stopped seeing. Logging your own behavior honestly, reading the patterns, and naming the glitch without flinching.
Part Two
Tracing the glitch to its root cause instead of patching the symptom. Where it came from, what it protects, and why it keeps getting re-installed.
Part Three
Shipping the fix. Small patches over grand rewrites, testing in production, and building a life that fails gracefully instead of silently.
Launch List
Drop your email and you'll get one message when the book launches, plus early excerpts before then. No spam. No infinite loop.
Launching 2026 · scratchyourglitch.com