This is the first post here. The plan is simple: write down the things I would otherwise have to rediscover a year from now.
Most of what I learn at work evaporates. A problem takes three days to understand, twenty minutes to fix, and then the whole shape of it is gone by the next quarter. The fix survives in a commit somewhere. The reasoning does not. This is an attempt to keep the reasoning.
What ends up here #
Things that misbehaved and why. Tools worth keeping and the ones I stopped using. The occasional opinion about how software gets built, held loosely enough to be argued out of.
Not tutorials. There are enough of those, and the ones written by people who just learned the thing are usually better than mine anyway.
Some posts will be about food, which I think about more than is reasonable.
How often #
When there is something worth saying. That is a lower bar than it sounds, and a higher one than a schedule. If you would rather not check back, there is a feed.
Thanks for reading. If this was useful, share it, or subscribe to the feed.
Published