- 1 min read
When I open the debugger
A short rule about when to step through code versus when to read it.
- 1 min read
My git rebase rules
A short list that has kept the history of my projects readable for a year.
- 1 min read
Why I keep a CHANGELOG.md, alone
A file for an audience of one, and why it has become the most useful file in the repo.
- 1 min read
When I write a test and when I don't
Three rules I follow, two I have softened, and one I refuse to bend on.
- 1 min read
One environment variable per concern
A small rule that has kept my config files honest for a year.
- 1 min read
A bug I left in for two months
Why the right time to fix it was the second I noticed, and what I am telling myself next time.
- 1 min read
When I start over vs when I refactor
A test I run on myself before I commit to either path.
- 1 min read
Why I don't use AI in production code (yet)
What I let an assistant do, what I do not, and the line that has not moved in a year.
- 1 min read
Reading code in the morning
A habit borrowed from a senior engineer that quietly changed how I work.
- 1 min read
Why I keep three GitHub repos open
How a small constraint on open tabs shaped what I actually finish.
- 1 min read
The shell aliases I actually use
A short audit of which shell aliases survived a year, and which I deleted on purpose.
- 1 min read
The quiet stack
Why I keep choosing boring tools for new projects, and the short list I default to in 2026.
- 1 min read
The cost of half-finished tools
Notes on cleaning up the personal AI tooling drawer that grew sideways for a year.
- 1 min read
My notes app is a folder
After a year of bouncing between note apps, I came back to a folder of plain Markdown files.