Joe Magerramov's blog

A few months ago I wrote about the new calculus of AI-based coding, how 10x velocity gains require corresponding investment in testing, deployment, and coordination, or the bottleneck just moves.

I've been doing agentic coding seriously for about six months now.

I've been having a small problem.

When I blogged about the challenges and opportunities of AI assisted coding, there were a fair number of questions about details of our experience.

Over the past three months, a team of experienced, like-minded engineers and I have been building something really cool within Amazon Bedrock.

If you work with multi-tenant systems you are probably familiar with the concept of throttling or admission control.

When working on distributed systems, it's not uncommon to need a piece of logic that executes across the entire system.

I was at an airport during a recent business trip, watching planes take off and land when I saw the iconic Boeing 747 take off.

In this post, I wanted to make a quick observation about batching as an underused technique in distributed systems.

The topic of software performance and efficiency has been making rounds this month, especially around engineers not being able to influence their leadership to invest in performance.

In a recent operational review, a colleague brought up how past feedback from me has influenced his team's avoidance of feature flags.

Well, hello there.