Blog posts fail because the implicit bar is “would I defend this in a code review?” That’s the wrong bar for 90% of what’s worth writing down. The right bar for a note is whether I’d say it to a colleague at lunch without qualifying it three times.
Ideas
Short notes, open questions, and things I haven't thought all the way through. Lower bar than the blog, on purpose.
All notes
3 totalWhen an agent does the wrong thing, the instinct is to reach for a better model. Usually the model was fine and simply didn’t know something I never told it: which of three similar files is the live one, that the test suite is flaky, that we tried the obvious approach last month and it didn’t work.
The interesting engineering problem isn’t prompting. It’s building a durable record the agent can read — one that survives across sessions and doesn’t depend on me remembering to mention things.
Everything else is adjustable. Column types, codecs, TTLs, even the partition key — all of it can be migrated with some pain. The sorting key determines which queries are fast and which ones read the whole table, and changing it means rewriting the data.
Worth spending a day on before inserting the first row.