miniblog.

← Back to all posts
Oct 27, 2018 at 12:27
4
The problem with being a software developer is that you stop seeing software as a fixed artifact that you can take or leave. Instead you start noticing things like 'this input would be better with type=email' and it's harder to accept poor designs.

Related Posts

Aug 6, 2026 at 09:35
1
As a kid I didn't particularly like bosses in games: they were a bother that you couldn't skip. Now, I see so many bosses with *amazing* designs. I think I'm just less intimidated. Platformers also let you wait until you're ready more often too.
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.
Dec 12, 2023 at 00:55
What software designs require clean slate 'revolution' implementations, rather than evolution? I can think of: borrow checking in a PL (existing code is unsafe), microkernels (architecture is too different from monokernels), and full REPLs (can't add type redefinition later).