miniblog.

My default assumption is that external libraries are better than what I (or an LLM) would write in a v1. The extra effort to publish a project generally signifies that the author has spent a good amount of time on the problem. I end up prompting LLMs to prefer external code.

Is there a good canonical name for autofixes, where a static analysis tool can apply a change to resolve an issue? Clang calls them fix-its, LSP calls them quickfixes.

Igalia's post on self-hosting CI runners is a masterclass in build engineering. It shows dealing with weird API constraints, but still finding good designs. I also learnt that some CI systems use OCR on Apple's installers to automate!