engineering/ — public portfolio & technical logs
Engineering Writeups
Un-gated technical writeups, debugging records, and architecture conventions.
engineering 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.
02Debugging 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.
03Green 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.