Posts

In the first post of this series, I mentioned that git distributes its objects across multiple directories, chosen in a specific way.

In this post, we’ll look at how and why git creates them.

Every file you track, every commit you make, amongst other specific things, are snapshots that live in one place: git’s objects database.

In this post, we’ll discuss the general anatomy of Git objects, and how git it stores and reads them.

My fiancée hit a git edge case I couldn’t explain. So I did what any reasonable person would do — I rewrote git.

During our RabbitMQ v4.x migration preparation, we started seeing exceptions we couldn’t make sense of, which eventually started bringing down our services.

I used an AI agent to build meal and workout plans that would help me lose weight and deployed it to Cloudflare pages

A shell function I wrote to stop reaching for Sublime Text every time I need to write a Slack message.

At Python Discord, we use Ansible to set up a part of our infrastructure.

A “bad” pattern we had is that we always tested these playbooks in production. I say “bad” because I think this can be a pretty controversial topic, and I’ve worked in a lot of companies who do this, or cheated their way around it, but that’s off-topic for now.

This led us to setting up a way to easily test our playbooks, but on a similar environment, without running the risk of unintentionally performing an undesired/destructive action or whatever.

Upgrading to RabbitMQ v4 threatened to break our entire usage of Celery, more specifically tasks with ETAs.

At 8M messages/day with zero downtime tolerance, we needed a migration strategy that preserves delayed task execution while switching from classic to quorum queues.