Easy To Delete
programmingisterrible.com/post"Every line of code written comes at a price: maintenance." A post from 2016 starts there. What follows is eight steps toward code that is easy to delete, and they argue with each other. Step 1:...
All the hats. One head.
"Every line of code written comes at a price: maintenance." A post from 2016 starts there. What follows is eight steps toward code that is easy to delete, and they argue with each other. Step 1:...
Version 2.0.3 of a database driver is still downloadable today. The repo it came from has no version 2. It hasn't for years. Running since 2011. One name on almost every commit. Between 2018 and...
The last release shipped over two years ago. The changelog just stops. Reads as abandoned. A maintainer who moved on. Clone it today. It still runs. The one thing it does, it still does. It didn't...
Scripture as decision tool. Bring a dilemma. Get a structured read. Each verse cites itself. Old text. New index.
The discipline of shipping well. Sketch before build. Review before ship. Verify before done. Atomic changes. Convention, not framework. Tool-adaptable. A /command per step. Solo, or with a thinking...
Draft the message before sending. Hard things go better when said twice: once to yourself, once for real. Know what to say before you say it.
Spec first. Stack later. Describe the idea. Answer the architecture questions. Walk away with a deploy-ready zero-stack spec. $0/month is the architecture, not the budget.
AI policy, generated. Pick a preset. Tune the rules. Download AIPOLICY.md, AGENTS.md, CLAUDE.md. Drop them in the repo. The bots will read them.
A feed with a last page. A handful of discussions for the day. Read them. Close the tab. Study desk, not newsstand.