Blog
2026
- An agent that opens PRs all night makes you the bottleneck
- Acceptance criteria must be provable
- Let agents review behavior and intent too
- On-call has a new job description
- The codebase decides how small a change can be
- Humans out of the loop
- Build the harness before you hand the agent real work
- Whether you think AI can or can't, you're right
- AI writes fast. It doesn't know what's good.
- Two code review loops I handed to agents
- From doers to directors
- AI agents are running errands now
- The agentic test pyramid
- There is no fixed amount of work
- Let an AI agent take the first page
- Building a platform is a balancing act
- Don't just build with AI — learn through it
- Speed is only useful if you're going in the right direction
- Review the outcome, not the output
- Don't hire me
- Use AI agents to break your app
- If you can't one-shot your feature, it's a SKILL.md issue
- Turning your terminal into an AI dev team
- Coding agents need a faster feedback loop
- Every CLI should include agent skills
- A bad line of research is a hundred bad lines of code
- AI never would have installed left-pad
- Code was never the goal
- Vibe-coded apps need real security
- Code quality still matters
- My AI recruiter honeypot worked
2025
- Stay out of the dumb zone
- I got tired of writing bad commit messages
- Your tests that make network requests are flaky
- Cat and mouse at machine speed
- Over-engineering is just future-proofing gone too far
- Building a platform is raising the floor for everyone
- Ship as fast as possible, but not faster
- Describe the what, delegate the how
- Turn the shit around!
- Sparse is better than dense
- Better conversations make better software
- How do you know you've fixed a flaky test?
- Flat is better than nested
- I built an AI tool to write my brag document
- Complex is better than complicated
- Simple is better than complex
- Explicit is better than implicit
- Beautiful is better than ugly
- Build your team a garden
2024
- Behavior tests tell you why the code exists
- Leave on-call better than you found it
- Test the sad path
- Slow down to speed up
- Stop counting incidents
- Write less about the options you rejected
- Rules tell you what, principles tell you why
- False alarms train you to ignore real fires
- Today I learned: There are three kinds of jitter
- Use example.com in your tests
- Go wide, then go deep
- Tests are for your future self
- Throw something back
- Upgrade your dependencies before you have to
- HTTP and the database don't belong in the same file
- Security adoption is a developer experience problem
- LeetCode interviews are on borrowed time
- Deploy is not release
- The slow part is between the boxes
- Measure your leadership by your absence
- Make the change easy, then make the easy change
2023
2018
2017
- Microservices are a team decision first
- Communication should take the shortest path
- Agile is about people and results
2016
2014
- Datomic performance with clause ordering
- Setting null values in Datomic
- Clojure protocol namespaces
- Mixpanel mock
- Implementing Clojure protocols
- Null object in Groovy