-
Here’s a pitch for the maintainers of Homebrew: make
brew updateandbrew upgradealiases of the same command, then addbrew update brew(orbrew upgrade brew) to upgrade Homebrew itself. End this confusion once and for all. -
Well mark this one off your bucket list: appearing in someone’s travel vlog recommended to you by the YouTube algorithm. 😄
-
📘 Devlog
3rd March 2026
This is a crosspost from devlog.lmika.org. I’m going to try and write posts about what I’ve been working on over there, while crossposting them here. Original post was made using Weiro, another attempt at a blogging CMS I’ve been working on.
Oof! Everyone’s building blogging CMS’s now, apparently.
Since starting work on this project, I saw one other announce their own CMS that was vibe-coded with Claude. No shame in that: making something that works for you is part of the joy of participating in the Indie-web. I did take a brief look at it, and dismissed it because it was written in PHP. Yes, I am a snooty developer that looks down on those using PHP (it’s just so annoying to deploy; although credit to this person, they did prepare a Docker container).
Continue reading → -
Oof! Everyone's building blogging CMS's now, apparently.
Since starting work on this project, I saw one other announce their own CMS that was vibe-coded with Claude. No shame in that: making something that works for you is part of the joy of participating in the Indie-web. I did take a brief look at it, and dismissed it because it was written in PHP. Yes, I am a snooty developer that looks down on those using PHP (it's just so annoying to deploy; although credit to this person, they did prepare a Docker container).
Weiro is not vibe coded. Much of it is written by hand. Not all of it, mind you: I am using agents to help with the more mundane stuff. But the models, DB schema, and much of the UI is hand-rolled. And I'm conflicted as to whether that's the right balance. Progress is slower: these vibe-coders are whipping up CMS's in the same time it takes me to add a single feature to it. And there are probably better things I could be doing other than adding one more CMS into the world (although when my mind whispers that doubt, it usually suggests watching TV or doomscrolling as an alternative, so there are certainly worse things I could be doing).
I haven't stopped working on it yet, so here's a brief update. I've got a version of it up and running in Coolify. It currently supports posts at the moment: both draft and published via Netlify. Much of the work was just making the writing experience feel natural, given that working on posts is probably the core feature of any CMS. So there's a very large window for the post body (maybe a little too large), and there's a Cmd+S keyboard shortcut for saving updates. I would like to add an auto-save feature, but I'm not entirely sure how best to do that server side, so I may settle for something that's browser only, just to save work for when the browser crashes or has no network connection. I'm also working on uploads, so there shouldn't be too much time before I can start sharing screenshots.
-
Oof! As a non-American, it’s sometimes a little hard to listen to Ben Thompson.
-
I do wonder if some of the patterns we’ve been using in software engineering, like multi-repo micro-service architecture, is actually a determent to agent coding. Those were deployed to help human developers coordinate, but it subdivides the possible area for agents to operate in. A monolith in a single repo, remarkably, may actually be better here.
-
How is it that people making screenshot mark-up apps still don’t understand that the blend mode for highlights should be multiply, not mix with alpha. A real highlighter would keep the text black, and won’t produce obvious overcoating. This just looks like I’m smearing yellow paint everywhere.
-
Oof! Glad that’s over.
-
You offer me Parmesan cheese for anything, you’re not getting it back.
(And lo! The floodgates, they open.)
-
It’s funny how some days, your overthinking of what to post results in nothing being written. This is me not overthinking it (with a bit of assistance from alcohol).
-
📘 Devlog
Hello
This is the inaugural post of Devlog, where I'm planning to write on what I'm working on. This post was created using Weiro, a new blogging CMS I've been working on. This post is little more than a test to see if the deployed version of Weiro is working. I'll post more about Weiro in later posts. For now, I just want to make sure this is being published correctly.
Continue reading → -
The Colour of Production
On the colour-coding system used for different development environments. Continue reading →
-
A bit frustrating that I asked my IDE to rename all instances of a method, and it did around half of them, ignoring the interfaces the type implements. I know Go interfaces are different to Java interfaces, but if the type checker passes already, rename things such that it remains that way.
-
This is green grass. A week ago it was brown grass that hasn’t seen rain in about a month and a half. What a difference a week and two rainy days makes.
-
Been riding the Metro tunnel to work in the morning, but I think I’ll switch back to my old commute. I’ve been touching off after 7 AM which means I’m losing out on the free travel coming into the city. Noticed this after seeing the top-up alerts come through more frequently.
-
Coding agents may help with coding, but it’s been my experience that the biggest time sink in software is dealing with all the rubbish associated with micro-services. Troubleshooting dozens of services, trying to see why they’re not talking to one another. Ain’t no agent that can fix that.
-
🔗 Pixel Envy: On Software Quality
I am somewhat impressed by the breadth of Apple’s current offerings as I consider all the ways they are failing me, and I cannot help but wonder if it is that breadth that is contributing to the unreliability of this software. Or perhaps it is the company’s annual treadmill.
I’m almost certain that the devs at Apple are not happy with shipping software that doesn’t match this quality threshold. They’d fix all this issues with Tahoe and iOS 26 if they could (well, the one’s that are not just bad designs). They just don’t have the time to do so.
Hardware takes months to setup, and once the lines are ready, it’s expensive to change them. So there’s huge resistance to change it near the end of the release cycle. Software’s malleability, in this respect, is a blessing and a curse. So easy to change, meaning that those making the decisions don’t see a cost in making these changes in the 11th hour. After all, it’s “just” software. But established software products are also resistant to change, and adding more cruft on the top just makes the change harder. Rather than fix things, devs spend all their time trying to get the bodged code working in concert while trying to meet the deadlines set from those that need features to sell. The result is lower quality software.
There’s no escaping the “scope, quality, time: pick two” maxim.
-
Will the solution to my problems really be at the end of an infinitely long social media feed?
Well, I don’t know. I haven’t reached the end yet. 😛
-
Missed my tram but thanks to the horrible traffic due to the rain, managed to catch it by walking to the next stop. Managed to lap the tram before it too, before it reached the dedicated track section.
-
🔗 Steve Yegge: You Should Write Blogs
An oldie but a goodie.
The last big problem I grapple with is biting off too much for a single blog. I find that if I can write a blog in a single sitting, it’ll usually seem worth publishing, at least at the time. […] If I can’t write it in one sitting, I feel like I don’t have something concrete enough to say. […] I can only do that with coding, not writing.
Yeah, I suffer from this too. I need to hit publish soon after writing the first draft, otherwise the resistance to finishing it gets too great.
-
The thing about DNS is that you’ve got one chance to get it right, otherwise your SOL for a good 15-20 minutes.
