► A TECHNICAL BLOG

AGILESCRIBE

Distributed systems. API design.
The craft of building software that actually holds up.
Written by engineers, for engineers.

Read the Blog →

* No content mills. No fluff. No “it depends” without the rest of the answer.

~/agilescribe/posts

$ ls posts/

distributed-systems/ api-design/

devops/ architecture/

$ cat README.md

# Complexity is not a feature.

# Write code someone else can read.

# Ship early. Observe. Iterate.

$ _

// what we cover

Topics

The intersection of how systems actually work and how engineers actually think.

fn distributed-systems let api-design str microservices var observability type devops fn architecture let systems-design str testing var performance type software-craft fn consensus-algorithms let database-internals

// recent posts

From the Archive

~/posts/microservices-monolith.md

[architecture]

Why Your Microservices Are Secretly a Monolith

Service boundaries drawn in anger are service boundaries drawn wrong. The org chart is not an architecture diagram.

READ →

~/posts/rate-limiting-vs-throttling.md

[api-design]

Rate Limiting Is Not Throttling: A Love Story

Two concepts everyone conflates. One subtle difference that matters a lot when 3am pages you.

READ →

~/posts/observability-not-monitoring.md

[observability]

Observability Is Not Monitoring (And That’s the Point)

Monitoring tells you something broke. Observability tells you why. Here’s how to actually get there.

READ →

// philosophy.md

We Believe In

Code that reads like a story.
Systems designed to fail gracefully, because they will.
Complexity earned, not assumed.
The second engineer having the same chance to succeed as the first.
Good defaults and explicit overrides.
Distributed thinking for distributed problems.
Documentation written like your future self will read it. Because they will.

Start Reading.

Everything here was written by someone who had to debug it at 2am.

Go to the Blog →