miniblog.

← Back to all posts
Feb 19, 2014 at 17:37
The difference between a good API and a great API is largely down to the behaviour in the dark murky corners.

Related Posts

May 25, 2026 at 15:13
2
Go has an os.Root API that allows you to enforce all paths are subdirectories of a given root. It fixes users accessing foo/../../../etc/passwd and similar. Seems like a really nice solution for a relatively common problem.
Traversal-resistant file APIs - The Go Programming Language
New file access APIs in Go 1.24.
Dec 31, 2025 at 08:29
7
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!
Web engine CI on a shoestring budget
Web engine CI on a shoestring budget
How we built a CI runner orchestration system that halved Servo’s build times for only 300 EUR a month.
Sep 14, 2025 at 13:28
47
I'm surprised by how many different weather forecasts I can get out different apps. Surely there aren't many API providers for weather predictions? Alternative conspiracy theory: do weather apps that predict nicer weather get more downloads?