Pinned
Start Here: A Plain-English Map to Understanding AI
New here? This is the front door — how AI works, how to use it, and how it affects you, organized into three paths so you can start exactly where you are.
Aug 19, 20266 min read
Command Palette
Search for a command to run...
Latest articles
How to Prioritize Technical Debt Without Arguing About Ugly Code
Two meters, two commands, and a four-box map for deciding what to fix, what to schedule, and what to leave alone.
Oct 7, 202610 min read
The 3-Line Diff That's Harder to Undo Than Your Rewrite
One-way door decisions in software, Hyrum's Law, and a two-question test for what becomes permanent
Oct 6, 202612 min read
Why Software Estimates Are Always Wrong: It's the Addition, Not the Guess
Right-skewed tickets, merge points, and a 15-line Monte Carlo script that turns your sprint into a 50% and a 90% date
Oct 5, 20268 min read
One-Way Door Decisions in Code: The Copy Test for Spotting Them in Review
Reversibility isn't about how big a change is. It's about how many copies of it exist where you can't edit them.
Oct 4, 20269 min read
Which Developer Skills AI Replaces Next: Sort by the Cost of the Check
Difficulty never predicted what gets automated. Verification cost does. Here is how to run the test on your own task list.
Oct 4, 202610 min read
The Sum Is the Bug: Why Accurate Software Estimates Make Late Projects
Every task passes its estimate check. The project fails anyway. Here's the reproduction, the root cause, and the fix.
Oct 3, 20269 min read
git blame Is Pointing at the Wrong Commit
How to find out why legacy code exists before you delete it
Oct 2, 20269 min read
The Knew-Said Gap: How to Communicate Project Delays Before They Cost You Trust
Every engineer misses dates. What people remember is how long you sat on it.
Oct 1, 20269 min read