Two hundred decisions

This week, after a little under two years of having adopted the practice, Buttondown has minted its 200th decision log. This is a practice very similar to RFCs or ADRs, but I prefer the term decision because it's both A, used for a variety of non-engineering purposes, and B, sounds a little less lame. The practice itself is extremely simple and there is no catch. It goes something like the following: Decisions are any non-trivial choice made for a specific reason. The context behind a decision is very hard to retrieve after the fact and grows in difficulty over time. The ability to revisit this context and update, invalidate, or buttress it is extremely useful in a variety of reasons. Our decisions range from the monumental-yet-concise: --- id: "0002" title: What domain should we use now that we have buttondown.com? date: 2024-05-14 status: implemented --- We should shift to buttondown.com, but the process of doing so is very unclear and we need to take it slowly + carefully. to the…