AI Moved the Bottleneck — and this time it landed in product
We ran out of stories. Our AI pipeline moved faster than product could spec new work. The bottleneck didn't disappear when we shifted left — it migrated.
Thinking out loud about AI, quality, and what it means to build software that actually works.
We ran out of stories. Our AI pipeline moved faster than product could spec new work. The bottleneck didn't disappear when we shifted left — it migrated.
AI makes seniors faster and juniors easier to skip — right when the industry needs more seniors, not fewer. A pipeline problem, not a productivity story.
Introducing the ADLC — the Agent Development Lifecycle. The loop that governs how you calibrate AI agents to produce reliable output.
How 15 specialized agents go from ADO story to shipped PR — orchestration, context management, quality gates, and drift detection.
Author agents enforce quality structurally — rating AI output, retrying on partial passes, and escalating when something is fundamentally wrong.
Without a feedback loop, your agent skills teach stale patterns — or worse, propagate security rules that were never right.
The architecture that cut per-session agent context by 85–89% — without losing a single useful rule.
Not all agent context is the same. The difference between skills, instructions, and scripts determines whether your agent stays focused.
Using the most powerful model for everything isn't a strategy — it's expensive and slow. Here's how to match models to tasks.
A single generalist agent doing everything sounds simpler. It isn't. Here's why specialists produce better output and preserve context at handoffs.
AI isn't replacing QE — it's making the discipline more essential. The judgment behind good testing is exactly what AI can't supply.
Prompt engineering isn't new — it's a repackaging of everything good engineers already know about communicating intent precisely.
A practical intro to Artillery — a modern load testing tool you can drop into your CI/CD pipeline. Know your code can handle the spikes.
Testing trends roundtable for 2022 — what the industry expects, what's hype, and what's actually worth your attention.
Write automated tests against your infrastructure code using LocalStack to mimic the AWS cloud environment — no AWS account needed.
A fireside chat for manual testers breaking into automation — real stories, practical advice, and how to land that first SDET role.
The pandemic changed how we work almost overnight — and its impact on quality engineering, our roles, and our processes ran deep.
A hands-on workshop walking from manual Postman collections to running automated functional API tests in a CI/CD pipeline with Newman and Docker.
Contract tests verify integrations will keep working — even when teams deploy independently. A practical guide to Pact and Pact Broker.
Quality Assurance was a checkpoint. Quality Engineering is a discipline. SDET is how it's practiced — in code, not process docs.
The tests that actually catch bugs are the ones nobody wants to write — negative cases, boundary conditions, and data-driven permutations.
High coverage metrics feel safe. But chasing 100% can give you a false sense of security while hiding the tests that actually matter.
Selected for GTAC 2013 at Google NYC — how we used code injection to track which APIs our automated tests actually exercised.
Most teams have an inverted pyramid — heavy on E2E, light on unit tests. Here's how to audit and rebalance the test portfolio.
Before Postman was mainstream, we were already testing APIs directly — faster, more reliable, and sometimes the UI simply doesn't exist yet.
What's in a name? Why QA gets treated as a cost rather than a contributor — and why the discipline needs redefining.
No posts found in this category.