What is this newsletter?
A newsletter documenting my journey in quality engineering and how quality engineers enable teams to build quality into the system.
I aim to post every two weeks, with each issue containing short summaries of my views on how quality engineers can help to build, maintain or lose quality focused on what I believe are the three core areas of quality engineering. These are the people, the processes and the products.
Who is the newsletter for?
This newsletter is for software technology professionals that want to
Develop their understanding of quality engineering, which is the study of how quality is built, maintained and lost in the software development life cycle
Enable teams to build quality into their products
Create a culture of quality within their organisations
Why subscribe?
After working in software engineering for 20 years, with much of it in various guises of Software Tester, I always asked myself, "How can we build better software?".
Catching issues before they affected users was important, but it required an army of testers and only worked if the system changed slowly. With software now evolving rapidly, test automation seemed like the solution, but relying solely on User Interface (UI) automation created more problems. We had three options: slow delivery, add more testers, or rethink how we deliver software.
I've spent the last seven years rethinking how we deliver software by engineering quality into the system, which I call quality engineering.
This newsletter documents my journey in trying to answer the question of how can we build better software.
Where to start?
Looking for some posts to get started? Then check out:
