A few years into my QA career, my manager asked if I had any tips for handling support tickets efficiently. I said of course, and put together a wiki page (this was before Confluence removed wiki from companies, anyways) describing exactly how I had my desktop set up. Most people never followed it. Some said […]
Inconsistent AI results come from a lack of shared understanding Read More »
You know the feature inside out. You have tested it, broken it, rebuilt the test suite around it twice. So you ask the AI to generate a few test cases. Save yourself twenty minutes. What comes back looks reasonable. The structure is right. The naming conventions are close enough. Then you start reading. The first
You were promised speed. You got a new job instead. Read More »
I’ve been seeing a lot of posts on LinkedIn recently that make the same claim: speed of writing code was never the bottleneck in software engineering. The real bottleneck was always thinking, choosing the right thing to build, understanding the problem. AI has just made that painfully obvious. I partly agree, but the framing is
Why the bottleneck was never just about thinking Read More »
Every time the topic of using AI for code reviews comes up, someone will eventually say that it is like letting the AI mark its own homework. It sounds clever. It also sounds responsible. Underneath it sits a familiar discomfort about oversight, trust, and professional judgement. As an analogy, it points attention away from the
Review as analysis, not authority, when working with AI Read More »
Sometimes I despair about the QA profession. Not because the work is hard, or because quality is complex. Both of those are true, but they always have been. What gets to me is where so much of our collective energy still goes. We have much bigger fish to fry. We have the tools to do
AI did not break testing Read More »
That day I rage quit my project It finally fell apart over a UI reskin. I had an application that mostly worked. It was not polished, but it was coherent, testable, and good enough to keep moving. When I asked the AI to reskin it using my brand colours, what I expected to be a
Stop vibe coding before you delete your repo Read More »
When I look at the current excitement around AI in testing, I cannot help feeling a sense of déjà vu. I felt the same thing when the first wave of no code and low code testing tools arrived. At the time, vendors promised that these tools would democratise testing, eliminate the need for technical skills,
A More Balanced AI Story Read More »
If you work in testing or quality engineering, you know the feeling.You see risks early. You spot patterns before anyone else. You raise concerns because you care about what happens next.And yet the conversation stalls. People nod politely, then move on. It is frustrating. Not because you want attention, but because you want to make
Become the tester people listen to: introducing Stakeholder Ready Read More »
“What do feelings have to do with quality assurance?” This question emerged from a question on LinkedIn I posted this week, asking QA engineers what feels worse: finding a critical bug right before release, or being known as the person who always blocks releases. While the post generated significant engagement, what truly caught my attention
From Gatekeeper to Guide: Why Emotions Matter in Quality Engineering Read More »
When I first joined a rapidly growing startup as the solo tester for the web team, I made every mistake in the metrics book. Fresh from an enterprise background, I tried to measure everything. Six months and countless spreadsheets later, I had plenty of data but no real insights. Here’s how I turned it around.
From Drowning in Data to Driving Decisions: A Solo Tester’s Journey Read More »
