Quality professionals are fighting the wrong battle

Quality professionals are fighting the wrong battle

I read a post on LinkedIn this week that went, roughly, like this. The level of quality in software has never been as low as it is right now. We as quality professionals have been fighting for years to raise it, and now everyone is chasing speed, more lines of code faster, everything is broken, and nobody seems to care. Someone replied underneath, in the way only LinkedIn replies do: nobody cared about quality before AI either, so why did you expect that to change now?

The back-and-forth that followed went in the usual direction. Someone mentioned professional software craftsmen who did care before and still do. Someone else brought up the analogy that AI is a second industrial revolution. The frame kept coming back to craftsmanship on one side and slop on the other, with the industrial revolution doing real work in the middle, as if the lesson of that period were obvious and on the side of the craftsmen.

Quality professionals are fighting the wrong battle Read More »

Your team doesn't have an AI problem

Inconsistent AI results come from a lack of shared understanding

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 »

Why the bottleneck was never just about thinking

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 »