Gary Hawkes | Comments
ACCELQ builds tests in plain English, no code, cuts maintenance 70%. Book a demo to see it across your entire stack!
My fear with this framework is it implies that AI is a "must use tool", hence a framework is needed to ensure that the AI is performing as we would want. It implies its more important to make sure AI is right, than getting the job done. AI should be nothing more than an advisor where we ultimately take responsibility for whether we use its findings or not. It shouldn't be about working on the AI to make sure it gives answers that are good enough where we can renege on our responsibilities.
I mentioned this in a club post. Quality is about balancing cost, quality and timescale. To improve, we need to get cheaper and/or better and/or quicker. How many articles do you see from people or vendors about using AI to be better? I'm seeing those outside QA, the focus is always on cheaper and faster, never on better.
Got them all...thanks to Ady's tip 😁
- For my role, next year I want to kind of maintain the new efficiency we've found, but look at what we can do and influence to reduce our unplanned release and support ticket levels
- Keep building my personal brand but finding where I fit and have the most influence. More meetups, more MoT articles and do a talk.
- Maintain my health regime, look after my own mental health better. Apparently I do bottle my anxieties without knowing so I clearly need to talk more, as well has help others
Glad to have caught up with this talk as on the day I was attending a workshop. Excellent talk Jitesh! 👏
He looks like he's missing a cigar...
Ship it, I've marked these accessibility bugs as low priority.
No there's a profile piccie!!
Very good points on letting go. It took me many years to thinking recognition is for getting praise for my ideas an initiatives, but the biggest victories are when the people around you take you initiatives and treat them as their own. When you think about it, there isn't better recognition right?
Thats a brilliant point about more collaborative training between roles. I've never thought of that as a problem, but it is 💡
Ha ha!! Love it 😂
Gary Hawkes
Head of Engineering
He/Him
Software QA Lead and tester who loves to see people grow, processes continuously improve and help organisations understand and support Quality Engineering. Recently promoted to Head of Engineering (Jul 2026).
Open To
Write
Mentor
Podcasting
CV Reviews