Backend & databases
I spend a lot of time working somewhere between the application and the database — building APIs, tracing weird issues, looking at slow queries, and figuring out why something that worked yesterday suddenly doesn't.
Backend · Infrastructure · Automation
I like understanding how things work behind the scenes — from the API and database to the Linux server running them. This is where I write about what I build, what breaks, and what I learn along the way.
I spend a lot of time working somewhere between the application and the database — building APIs, tracing weird issues, looking at slow queries, and figuring out why something that worked yesterday suddenly doesn't.
Most of my infrastructure work starts with a Linux server. I run services in containers, deal with networking and reverse proxies, move things between servers, and try to keep everything simple enough that I can still understand it months later.
If I notice myself doing the same thing over and over, I'll probably try to automate it. Sometimes that means a proper tool, sometimes it's just a small script or a cron job that saves me from doing the boring part again.
Notes from projects, experiments, and problems I've spent time working through.
This is the first post on a site that has been a long time coming. I have wanted a quiet corner of the internet for a while — somewhere to write down what I learn, without the noise and the feed.
A lot of what looks like a scaling problem is really a maintenance problem. On a small VPS with a gigabyte or two of RAM you can run a surprising amount — as long as you keep the number of moving …
When people hear “blog” they often picture a database, a login screen, and a dashboard full of plugins. You can absolutely run it that way. But if all you are publishing is words, a static …
Working on something similar, or want to discuss a post? Feel free to reach out.