Gary Hawkes | Comments
ACCELQ builds tests in plain English, no code, cuts maintenance 70%. Book a demo to see it across your entire stack!
🎶 "Stayin aliiiiiiiiiiii-iiiiiiiiii-hiiiiiiiii-iiiiiiiiiive"🎶
How do you communicate confidence in quality to those outside QE, when the confidence is beyond just the correctness of what was built?
What do you do to set your career goals and motivate yourself to progress them, without having a likeminded team around you?
This was fascinating! So much so I saved to one of my private collections so I can go back to it. Thanks for sharing 🙏
Great Article Ishalli! Saved into my private influential articles collection. As our team has gotten smaller over the years we have had to adapt. We've been learning to be far more risk based.
What we're missing currently is that insight from customers. We're not close to them ourselves and the priority of the information flow from Product and Customer Success teams, is usually too specific to prioritise. However, we have been pushing a few more initiatives to influence that conversation 🤞
How would you store any context engineering templates so they can be re-used?
If your exploratory testing uncovers an area that may be an ideal candidate for automation, what steps would you go about communicating that to the developers/automators to get it done?
Interestingly, we have a Quality Gate but its not really a gate that we police. Its in essence a 15 minute prod deployment review to make sure everyone is happy from their perspectives before we ship it. So at the very least it needs a rebrand.
However, the one gate that is prominent is as Phillipa mentioned, i.e. Agile...but testing after dev. We are moving in the right direction by doing more to influence quality earlier so that we need to test less but there's a journey to be had for sure.
This is really cool to read. It certainly parallels with my experience working with devs using coding agents. If their focus is "to build something", thats what their prompts will reflect and focus on. They won't reflect Product context, quality context, support context, security context or user context. Thats primarily why our roles a changing and needed, more than ever.
I'm guilty! I'm jumping across gaps all the time 🤚. But what I try to do is focus on influencing responsibilities that can act on knowing who should fill the gap or those who probably should own that responsibility. I make it explicit, "I will help with this" not "I will do this". But, I still fall into the trap sometimes where I enjoy filling that gap and that my efforts are making a difference.
I found this chat really reassuring 🤗. As much as I loved MoTacon and felt it was the best experience of my professional life so far, I had moments where I was overwhelmed. So its great to hear people like Chris also share they felt that too. I'm also balancing the things I think I should do in the community, with acting on those things that feel right at the time to share with the community. Thanks for sharing this 🙏
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