$ cat about.txt
arenarium infinitum.md
// a running log of what I build, play, live through, and make up
# engineering — personal experience
$ ls posts/ --sort=date --limit=6
recent posts
01One Call Instead of Twomcptime-to-answerThe discount case from part 3, answered again through a single tool call instead of two manual steps: the joining moved into code, the reading moved into a document, and asking again has no per-token bill on it.
02The Drive Outside the MachinepersonalA 512GB compromise accepted at purchase, and the second purchase it took to live with it.
03Hardware Is the AccesspersonalWhy the most expensive thing I own was the cheap option, and why a year of waiting would have cost more than the money.
04Debugging Production Without Leaving the IDEjetbrainstime-to-answerThe fastest way to tell a code bug from a config bug is to ask the database and the API the same question without leaving the editor — a chain that settled a production discount complaint in minutes, and the finding was that no bug existed: the sale had ended the day before the customer bought. The real lesson isn't the tool; it's the habit of handing a value you're already looking at to the next question you need answered.
05Green Caretsjetbrainstime-to-answerTest results that land in the editor — green carets on passing lines, every failure a click from the assertion that broke it — remove the manual rejoin between a failing test and the code that caused it. On a legacy JavaScript codebase, removing that rejoin changed how this code gets edited at all.