Reframing Quality Beyond Code: "May the bridges I burn light my way"
The article discusses the evolving definition of quality in software engineering, emphasizing the importance of measuring outcomes beyond just successful deployments. It advocates for a three-tiered quality ledger that includes shipped features, rollbacks, and informed decisions to better assess engineering efforts. The piece highlights the role of AI in enhancing real-time monitoring and anomaly detection during software rollouts.
- ▪Quality Engineering is shifting from merely ensuring products are built correctly to ensuring the right products are built.
- ▪A three-tiered quality ledger categorizes outcomes into shipped, rolled back, or informed a decision to better evaluate engineering ROI.
- ▪Celebrating rollback rates can indicate a healthy experimentation culture that prevents user friction and product degradation.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 338996) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Paradith Posted on Jun 3 Reframing Quality Beyond Code: "May the bridges I burn light my way" #mvt #programming #ai Quality Engineering and software leaders are traditionally tasked with answering a deceptively simple question: Is this software good enough to ship? For years, the industry answered this through regression testing, automation suites, and staging environments designed to prevent bugs.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
