4/26/2026

GitHub's Status Page - Incident with Pull Requests.

3/26/2026

3/19/2026

3/13/2026

3/6/2026

2/27/2026

2/20/2026

It's been a bad couple of weeks for GitHub reliability, but how does this compare to their previous performance? I pulled some data from their status page to find out.

Is Plur1bus secretly about AI? Officially, no, but that didn't stop me seeing shadows of GPUs in almost every scene.

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. What we consider to be "good" CI today may be very different from tomorrow's definition

It's been a month and a half since I started working on a Git-backed REST API. High time to wrap it up and answer the dang question already!

My git-backed REST API is performant and can even handle concurrent requests, but is it production ready? Here's how I went about making it stable.

After 18 months of working on Ocuroot, I think it's time to move on. It's been a heck of a ride and quite the learning experience!

You may or may not have heard about trees in Git, but you've definitely worked with them! This post provides an overview of what trees are, how they fit together and walks through an example.

YouTube video by Welch Labs

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

GitHub Actions pricing update: Discover lower runner rates (up to 39% off) following a major re-architecture for faster, more reliable CI/CD.

Running a REST API off of the Git CLI tool was slow to say the least. Can I make the API a little faster by interacting with the Git server more directly?

Git is basically a fancy file store with history, so can it be applied to use cases other than source control? Come with me as I try to repurpose Git into a backing store for a simple REST API