Gary Hawkes | Comments

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 🙏

Great conversation. Engineering often get look at as the sole responsibility for shipping faster. But when we step back we realised that engineering can only go as fast as every process from Product to the customer will allow. I think Quality Engineering and Continuous Quality practices, will be uncovering the friction in each discipline and influencing the discussions on how we reduce unnecessary friction or manage the friction we can do nothing about, better.

100% support. I haven't even completed my first year but I've been able to extend my membership by contributing articles, course content etc. That's an easy sell to bosses, as long as we put the work in. Professional membership has changed me for the better- personally and professionally! 🙏

Brilliant article. Over the years, my QA team had reduced from 13 to 4. We have had to react and do things differently as the luxury of lots of dedicated resources has gone. This is an inspiring article that will help me tackle that, so I've saved it. Thanks for sharing 🙏

You know what, I wasn't sure when I started to read this as to what new things it will open up...BUT as soon as you brought in the ISO and IEEE standards amongst all the other sources, this is a really thought provoking read. Are the industry standards keeping pace with Quality Engineering practices? Which are way off the pace. Genius Ady! 👏

I used to have a whale mug where the handle was in the shape of its tale. Whilst I admired its accuracy in design, fish tales are not exactly designed to be held.