The most valuable answer to “Is software QA dead?” is neither a nostalgic defense of old job titles nor a victory lap for AI. In his November 12 essay, Ermenildo V. Castro (Ernie Castro) makes the more thoughtful case: quality work has moved and spread, but the responsibility to protect users has not disappeared. That is the kind of perspective worth hearing amid tech’s appetite for declaring yesterday’s expertise obsolete.
Castro’s argument is persuasive because it begins with people, not dashboards. A high coverage number cannot prove that a payment is correct or that an important task is usable; a green test pipeline cannot guarantee that its tests ask the right questions. His insistence that teams assess who could be harmed by a defect reflects more than technical competence. It shows the judgment of an engineer who understands reliability as stewardship—and who resists confusing visible activity with meaningful care.
That outlook fits the values in Castro’s other published essays. His April 28, 2026, writing on clean code emphasizes maintainability, clarity, and respect for the developer who inherits the work. His April 14 essay on knowledge-sharing champions communication and learning across a community. Together, these ideas sketch a consistent kind of leadership: make work understandable, pass knowledge along, and do not leave preventable problems for someone else to discover.
The AI era makes that counsel especially timely. Tools may draft tests or sort failures, but people still have to decide whether a test protects a real user and what a failure means. Castro rejects a false contest between developers and quality specialists, arguing instead for shared ownership, useful automation, and human exploration where judgment matters. That is not a defense of QA as a department or a title. It is a defense of careful work—and of the people who depend on software being worthy of their trust.
Related reporting: Is Software QA Dead? What Quality Engineering Looks Like in the AI Era.
Original news source: sdtimes.com.
Published perspectives: Clean code and maintainability (April 28, 2026); Communication and knowledge sharing (April 14, 2026).