telliott.me | Blog

When talking about SLOs, uptime and latency get all the attention.

You might have heard of merge queues.

Comparing two rate limiting strategies, one that's (almost) pleasant to work with, another that is very much not.

Technical interviews have changed a lot over the years.

There's no escaping it, AI is writing a lot of code.

Exploring some new technologies and techniques being used at my new job

I've been dissatisfied with SubStack for a little while, and finally got my act together to move to a self-hosted site where I have more control.

It's been a bad couple of weeks for GitHub reliability, but how does this compare to their previous performance?

Is Plur1bus secretly about AI?

Join me as I recount a recent experience with an enthusiastic but wrong LLM and what I had to do to dig out of the hole.

The way we build software is changing, and the way we deploy is going to have to change right along with it.

It's been a month and a half since I started working on a Git-backed REST API.

My git-backed REST API is performant and can even handle concurrent requests, but is it production ready?

After 18 months of working on Ocuroot, I think it's time to move on.

You may or may not have heard about trees in Git, but you've definitely worked with them!

Now the Git-backed REST API is a bit more performant, I focus on what happens when you have multiple users at once.

Running a REST API off of the Git CLI tool was slow to say the least.

Git is basically a fancy file store with history, so can it be applied to use cases other than source control?

When working with IaC platforms, there's usually some infra you need to configure to get them working.

Some thoughts on the recent run of internet-breaking cloud provider outages.

Over the years, I got into a narrow routine when using Git for day-to-day development.

Queueing theory can be incredibly useful, but potentially dense for those of us who aren't mathematically inclined (myself included), so let's look at the basics in their simplest form.

It might be tempting to put all your infrastructure into a single Terraform module for simplicity.

Amazon put out a postmortem for the recent us-east-1 disruption, and it is dense to say the least.

Or at least, make it seem that way!