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. 💣