Knowledge
Articles
Writing on quality engineering, testing strategy, and AI-assisted workflows.
Image sourced from the web
EngineeringOne Script, One Laptop, the Whole Stack
How to give every engineer a complete, disposable copy of a two-dozen-service platform with a single shell script: containers, schema from CI, seed data, stubs for the outside world, and a preflight that tells you exactly what to fix.
EngineeringMigrating Claude Code Context Between Machines
Claude Code's memory, sessions, and settings live on disk — not in the cloud. When you get a new machine, they don't follow your login. Here's what's worth migrating, how to merge it cleanly, and what to sanitize before it crosses the boundary.
EngineeringRunning Two Claude Accounts on One Mac
The commonly shared recipe for running two Claude Desktop accounts on macOS fails three separate ways on current builds. Here is what actually works — two isolated apps, two CLI profiles, shared context pools, and an auto-repatch script so the duplicate stays current.
LeadershipThe Audience Doesn't Experience Your Plan
What emceeing QonfX Singapore taught me about outcomes, quality, and Quality Engineering.
TestingMaking Exploratory Testing Visible
A good session produces more than bugs. It produces a record. Here is how to write session reports that communicate clearly, and how to use them to make exploratory testing visible to everyone who needs to see it.
TestingSession-Based Test Management
Exploratory testing without structure is just clicking around. SBTM adds accountability through chartered missions, time-boxed sessions, and a reporting format that makes the invisible work visible.
TestingUsing Mind Maps for Exploratory Testing
Mind maps help you think through a feature before you test it. Use them to generate test ideas, model the system, identify risks, and turn those ideas into focused exploratory sessions.
TestingWrite Test Charters That Drive Exploration
A charter turns exploratory testing into a focused mission. It gives you direction without deciding in advance what you will find.
TestingExplore Requirements Before You Test
Exploratory testing starts before you open the application. It starts with reading the requirements and knowing what to look for.
TestingWhat Is Exploratory Testing?
Exploratory testing is not random clicking. It is a disciplined approach to learning about a system and using that learning to design better tests in real time.