Field notes from the studio.
Short, technical writing on the things we run into shipping production software. Nothing recycled, nothing AI-generated.
Engineering essays, not thought leadership.
Every post is a problem we hit on a real engagement and the pattern we used to solve it. No vendor primers, no "10 trends" round-ups.
AI & LLM systems
Evals, RAG, fine-tuning, agentic patterns. Things that work and things that don't in production.
Architecture & trade-offs
The decisions you can't undo later. Postgres vs. specialized stores, monolith vs. services, sync vs. event-driven.
Delivery practices
Feature flags, observability, deploy automation, postmortems. The boring work that makes the rest possible.
Hiring & team-building
What we screen for, how we onboard, what makes a senior engineer at WAMO Labs different from one anywhere else.
Performance & cost
p95 latency, infrastructure cost per active user, runtime efficiency. Numbers we hold ourselves to.
Field notes
Short, specific things we ran into this quarter. Untheorized. The kind of writing engineers actually read.
Engineers shipping the work, then writing about it.
Every essay is by-lined. Every author has hands on the code they're describing. No ghostwriters, no marketing-team rewrites.
Hamid Khan, Founding partner
Architecture, sales engineering, the founder-engineer perspective. 11 years of shipped product across FinTech and HealthTech.
Engineering principals
The senior engineers who run engagements. Topics that matter: AI evals, multi-tenant architecture, delivery rituals.
Domain specialists
HIPAA, SOC 2, PCI DSS, payments rails. The people who actually take clients through certification, writing about how.
Guest engineers
Occasional posts from clients and friends-of-the-studio. Different perspectives, same bar for substance.
Things we'd rather not say.
Some content categories are intentionally absent. They waste your time and ours.
Listicles & "X tools you need"
If a post can be replaced with a Google search, we haven't earned your attention. We write only when we have a take.
Generic AI primers
You can read the OpenAI blog. We write about specific patterns we've shipped, not what an LLM is.
Recycled vendor content
If AWS, Vercel, or Vercel's competitors already published it, we don't republish a variant.
AI-generated drafts
Every post is written by a human who ran the code. The voice is real, the typos are real, the takes are real.
One letter, monthly
A round-up of what we shipped, what we learned, and what we're building next. No filler.