I'm Tom Usher, a Web Developer & DevOps Engineer based in lovely North Wales, UK.
I recently picked up the widely hyped Xteink X4 e-reader, in one of those moments where I can happily justify purchasing more tech in pursuit of improving my life.
Of course I immediately installed the open-source Crosspoint Reader firmware on the device, which led to a novel realisation. (heh)
It's hard to avoid the refrain that AI is out for our jobs. That all developers will be replaced by LLMs and we'll all have to brush up on our prompt engineering or just become gardeners (tempting, to be honest...).
But developers don't just write code, we also know how everything actually works. Which systems are held together with wishes and crossed fingers. We're deeply embedded in how companies operate, and more often than not, we're what's keeping the lights on.
The king of LLM blogging, Simon Willison, has a great overview on using LLMs to write code.
Using LLMs to write code is difficult and unintuitive. It takes significant effort to figure out the sharp and soft edges of using them in this way, and there’s precious little guidance to help people figure out how best to apply them.
Even if you’re not sold on how LLMs can boost your development, I’d highly recommend that learning to manipulate them to your benefit is a skill worth learning.
We are being boiled like frogs. It happened gradually, one algorithmic tweak at a time. What started as a way to connect with friends has become a system that gives the corporations that run social media control over what we consume and the ability to subtly shape how we think.
Frenck (lead engineer of Home Assistant) breaks down the state of his smart home. While you might assume the lead engineer of a home automation platform has everything figured out, it’s fun to hear that’s far from the truth.
…my dashboards are so bad that if I turn on the “Coffee machine” switch, it actually powers on my 3D Printer. 🤦♂️
I keep seeing examples of this - lead developers and experts in their field often don’t have the perfect environment - they are focused on the things they want to do and often the pursuit of the ideal environment falls by the wayside.
This is something I often need to remind myself about when I go on a yak shaving adventure tweaking my editor setup or finding the perfect tool for a job.
I love reading technical deep-dives in to system design and scaling. This post from Jaz (infrastructure at Bluesky) is a great read on how they balanced user needs with performance by finding where they could be ‘imperfect’.
By specifying the limits of reasonable user behavior and embracing imperfection for users who go beyond it, we can continue to provide service that meets the expectations of users without sacrificing scalability of the system.
There’s always sacrifices to be made in system design - I like the idea of defining a ‘reasonable limit’ for any one user and building optimisations around that limit.
If you have more than 1 server and a need to deploy multiple applications 'somewhere' on that cluster without having to micromanage - don't reinvent the wheel, just use Kubernetes. It's the industry standard for a reason, and you're not going to have a hard time finding help when you need it.
However, it's easy to forget that there's a class of service/business where this doesn't make sense. Many small businesses (if they're not using a PaaS like Fly), don't have the resources to run a Kubernetes cluster and 95% of the time, just need an app to run on a single VPS.
Andy Hawthorne writes a lovely summary of why it’s worth blogging:
When you write, you think better. When you think better, you create better.
I’ve just added Simon Willison’s link blog pattern to this site, hoping it will encourage me to write more, even if it’s just fleeting thoughts on a link like this one.
Whether you need help with a project, have a question, or just want to say hello, I'm always happy to chat.
Get in touch