Weighted load balancing has saved me more times than I can count. TL;DR: Weighted load balancing lets you shift traffic by percentage, making migrations, canaries, and production changes far safer than all-at-once cutovers. bencane.com/posts/2026-0...

Cut a new release of madflojo/tasks over the weekend. Mostly focused on maintainability improvements, cleanup, and hardening the codebase a bit more. Shout out to the friendly neighborhood LLMs for taking up most of the grunt work. github.com/madflojo/tas...

YOLO Is a Terrible Strategy for Validating Production Changes. TL;DR: Validate production changes in layers—canary, shadow traffic, synthetic traffic, and smoke tests—so customers don’t become your QA team. bencane.com/posts/2026-0...

Deterministic routing is one of the most effective ways for distributed systems to reduce consistency problems at scale. tl;dr: Route requests for the same data to the same place to scale systems while reducing stale reads and coordination overhead. bencane.com/posts/2026-0...

I was looking up a configuration for HA Proxy and came across an article that had all the answers I needed. But it seemed familiar somehow… Oh, wait, I wrote it 10 years ago. 😅

Running the same microservice in multiple platforms can sometimes be better than centralizing it. TL;DR: Reuse the codebase locally to reduce coupling, latency, and the impact of failures. bencane.com/posts/2026-0...

Recently, I published a few of my personal agent skills that I’ve been using for a while now. 📋 Review This Review a codebase, docs, or even blog content. Get a quality score and recommendations. github.com/madflojo/rev...

Every time a credit card is swiped, a correlation problem has to be solved in real time. In low-latency systems, you can’t wait for each request to finish. I wrote a deep dive comparing how payment systems and modern distributed systems handle this. 👉

If you’re migrating a system without shadow traffic, you’re taking on unnecessary risk. tl;dr: Traffic mirroring lets you send real production traffic to a new system without affecting users. It’s one of the safest ways to validate behavior before a cutover. 👉 bencane.com/posts/2026-0...

Agent Skills aren’t just for actions; they’re for institutional knowledge tl;dr: Most institutional knowledge lives in docs no one reads. Agent Skills let you capture that knowledge (frameworks, patterns, constraints) so agents can discover and apply it automatically. 🔗

Saved prompts are dead. Agent Skills are the next step. 
tl;dr: Instead of manually calling prompts, agents can now discover and execute skills based on intent. Skills bundle prompts, scripts, and context into reusable capabilities. 
👉

Generating code faster is only valuable if you can validate every change with confidence. AI tools are making it dramatically easier to produce code. But if you can generate changes faster than you can test them, you eventually create more software than you can safely operate.

I’ve been experimenting with capturing how I want my Go code to look in an agent skill: github.com/madflojo/go-... I decided over the weekend to break it out into its own project and share it with others. It’s very opinionated, but I’ve found it successful so far.

When you go to production with gRPC, make sure you’ve solved load distribution first. One of the biggest gotchas when teams roll out gRPC isn’t performance. It’s load balancing.

Migrating the American Express Payments Network Twice with Zero Downtime. Modernization isn’t real until the new system takes production traffic. Here’s how we approached migrating from our legacy payments network to our new cloud-ready platform. americanexpress.io/migrating-th...

You may be building for availability, but are you building for resiliency? Many teams design for availability. Far fewer design for resiliency.

If you're into hearing about complicated migrations of mission-critical payments platforms, you should check out my talk tomorrow at Monster Scale Summit. At AMEX, we didn't just migrate the Payments Network once; we did it twice, zero downtime. www.scylladb.com/monster-scal...

When your coding agent doesn’t understand your project, you’ll get junk.

You can have 100% Code Coverage and still have ticking time bombs in your code. 💣