A growing collection of posts that define what QA actually is, what we do, and why it matters. Built from years of practice and honest thinking — not borrowed best practices. Start with What QA Actually Is if you’re new here.
In grad school I was researching how students debug their code. I came across something called Information Foraging Theory — the idea that people hunting for information follow certain scent trails, signals in the environment that promise high-value information for the least amount of effort. Like an animal following a smell toward food. I wasn’t...
Every discipline has a core skill. The thing that looks simple from the outside but takes years to actually develop. Developers have the ability to build systems — translating logic into working software. Product managers translate messy human needs into structured requirements. Designers make complex things feel intuitive. I’ve been thinking about what QA’s equivalent...
I recently learned what a “cargo cult” was. Apparently, there’s a story from World War II that goes something like this. When American forces set up military bases on remote South Pacific islands, they brought everything with them — jeeps, radios, canned food, medicine, aircraft. To the indigenous islanders watching from the treeline, the goods...
A few years ago I wrote about how a long pandemic shower helped me realize that software testing is really just collecting information about system behavior. That clicked for me. But the more I’ve worked in QA since then, the more I’ve realized that definition only answers what testers do — not why it matters....
I was three years into a QA career when the pandemic hit. Testing Manager at a tech startup, CS degree, the whole thing. You’d think I would’ve had a solid handle on what software testing actually was. I didn’t. Not really. I knew the definitions. I’d memorized them the same way I memorized Newton’s equations...
