Every developer I know has a strange relationship with their tools. We customize, we tinker, we migrate. And then one day we realize the tool we abandoned years ago still does the job better than the shiny replacement.
This post is a small public promise to myself to keep things boring and reliable.
Notes over tutorials. When I learn something new, I will write it here as a short field note: what I tried, what broke, and the one line that fixed it. No 3000-word deep dives — just the useful part.
Simplicity over cleverness. If a setup takes longer than an afternoon to rebuild, it is too complicated. Same for scripts, same for workflows.
Writing as debugging. Explaining a problem in plain words is the fastest way to find the misunderstanding hiding inside my own head. This blog is where I will do that explaining.
If you are the kind of person who enjoys quiet, practical notes about working with technology, this place is for you. The first rule of my toolbox has always been: write things down. So here we are — this blog is that rule, put into practice.
Top comments (0)