Newsletter
Deep AWS + AI engineering
in your inbox
This is the newsletter for engineers who want the technical detail, not the hype. Each issue covers a real problem from a production AWS or AI deployment: the CDK pattern that survived a real workload, the Bedrock AgentCore gotcha that cost an afternoon, the cost decision that shows up on the bill.
- ✓ A new write-up every Tuesday, only when it's worth your time
- ✓ Technical and specific: Bedrock, CDK, AgentCore, IAM, real code
- ✓ Written by me, not generated: the same voice as the blog
- ✓ No sponsors, no affiliate links, no weekly digests
No spam. Every email has a one-click unsubscribe link.
Recent posts: a sample of what lands in the newsletter
The harness is one integer column
The fix for a poison-pill row re-billing a model every sixty seconds forever was not a rewrite. It was one INT column, capped at five, incremented atomically in the database. The fix itself shipped with a gap, and that gap is the actual lesson.
Introducing the AI Architect Roadmap
Eight rungs mapping what shipping production Agentic AI on AWS actually takes, marked honestly as covered, strong, flagship or gap rather than filled in to look finished.
Not a Python tutorial: the patterns that bite in production agents
The senior-lens Python patterns that actually bite in a production agent loop: why boto3 blocking the event loop is the first one, and four more that follow from it.
You probably don't need to fine-tune
A post framed fine-tuning as a 2026 interview trap. Here is the AWS version: the ladder before you touch weights, the four job types and three serving paths Bedrock forks 'fine-tune' into, and what each one costs, priced today.
Your quality alert needs 32 samples
Part 3 left me a label-free signal that responds to a real regression. It does not come with a threshold. Here is where the line actually goes, what a false page costs, and why the reflex answer computes to a negative number.