[{"data":1,"prerenderedAt":49},["ShallowReactive",2],{"article-en-error-code-as-software-quality-indicator":3},{"article":4,"related":18,"prevArticle":38,"nextArticle":42,"availableLocales":46},{"id":5,"slug":5,"title":6,"excerpt":7,"content":8,"image":9,"date":10,"published":11,"status":12,"category":13,"keywords":14,"meta_description":15,"og_image":16,"custom_css":16,"created_at":10,"updated_at":17},"error-code-as-software-quality-indicator","[A hidden SQA indicator] Structured error codes","Error codes are not just an error-handling tool but an important indicator of software quality maturity. An SQA view of how error codes affect diagnosis speed, team collaboration and user experience.","\u003Cp>An SQA indicator that is often overlooked, yet very easy to recognise\u003C/p>\u003Cp>When people talk about software quality, most think first of test coverage, bug counts or system stability.\u003C/p>\u003Cp>But in practice, I have come to rely on a very concrete and often overlooked way to judge it:\u003Cbr class=\"hard-break\">\u003C/p>\u003Cp>\u003Cstrong>\u003Cem>Whether a system has ever had its error codes \"seriously designed\" often says more about its quality maturity than the features themselves.\u003C/em>\u003C/strong>\u003Cbr class=\"hard-break\">\u003C/p>\u003Cp>By this I do not mean error codes that are just numbers used as an index, but error codes with deliberate structure and meaning.\u003C/p>\u003Chr>\u003Ch3>\u003Cstrong>When error codes become a \"quality signal\"\u003C/strong>\u003C/h3>\u003Cp>\u003C/p>\u003Cp>I first really understood the value of error code design while reading Microsoft source code.\u003C/p>\u003Cp>In those systems, error codes are not arbitrarily defined integers. Using bit-wise AND / OR across 16 or 32 bits, they encode the source, module, type and severity of an error in a structured way.\u003C/p>\u003Cp>That was when I realised:\u003Cbr class=\"hard-break\">\u003C/p>\u003Cblockquote>\u003Cp>Error codes are part of the system design itself, not an add-on.\u003C/p>\u003C/blockquote>\u003Cp>\u003Cbr class=\"hard-break\">A very common pattern in practice is this:\u003C/p>\u003Cp>when a system grows large without a clear error code and error handling scheme, the team ends up spending a great deal of effort on \"finding the problem\" rather than solving it.\u003C/p>\u003Chr>\u003Ch3>\u003Cstrong>What does a system without error codes really cost?\u003C/strong>\u003C/h3>\u003Cp>To sum up the impact of lacking structured error codes in one line:\u003Cbr class=\"hard-break\">\u003C/p>\u003Cblockquote>\u003Cp>Diagnosing errors takes longer, the diagnosis is more often pointed in the wrong direction, and in the long run the customers you lose because of errors will be far more than you expected.\u003C/p>\u003C/blockquote>\u003Cp>\u003C/p>\u003Cp>On the surface, these systems are not entirely without error handling: there are error messages, logs, exception call stacks,\u003C/p>\u003Cp>and even some input-guarding logic.\u003C/p>\u003Cp>\u003C/p>\u003Cp>When something goes wrong, the team often has to spend a lot of time working out:\u003C/p>\u003Cp>\u003C/p>\u003Cp>\u003Cstrong>Is this a data problem or a system problem?\u003C/strong>\u003C/p>\u003Cp>\u003Cstrong>Which module threw the error?\u003C/strong>\u003C/p>\u003Cp>\u003Cstrong>Is it a variation of a known issue, or something entirely new?\u003C/strong>\u003Cbr class=\"hard-break\">\u003C/p>\u003Cp>Because errors were never defined in a structured way, everyone has to piece together the truth from experience, guesswork and endless back-and-forth.\u003C/p>\u003Cp>From an SQA point of view, this is a very clear quality signal:\u003Cbr class=\"hard-break\">\u003Cbr class=\"hard-break\">\u003C/p>\u003Cp>\u003Cstrong>The system never treated \"errors\" as a first-class design concern.\u003C/strong>\u003C/p>\u003Cp>\u003C/p>\u003Chr>\u003Ch3>\u003Cstrong>Error codes really reflect the designer's maturity\u003C/strong>\u003C/h3>\u003Cp>The real dividing line is usually not \"whether there are error codes\", but:\u003Cbr class=\"hard-break\">\u003C/p>\u003Cblockquote>\u003Cp>whether the designer already expected that problems will happen.\u003C/p>\u003C/blockquote>\u003Cp>\u003Cbr class=\"hard-break\">Mature system designers do not treat errors as exceptions. They treat them as certainties. Once you accept that premise, the role of error codes changes completely.\u003C/p>\u003Cp>They are no longer just a debugging tool for engineers. They become a carrier of information across roles, passing key information along the whole product line.\u003C/p>\u003Cp>That is exactly why error codes can almost be treated as a hidden quality indicator.\u003C/p>\u003Cp>What they reflect is not engineering skill, but whether the team has thought about \"how we will deal with problems together once they happen\".\u003C/p>\u003Cp>\u003C/p>\u003Cimg class=\"rounded-lg shadow-lg mx-auto block max-w-full h-auto\" src=\"https://cdn.sqa.tw/articles/1766298571782-tzggi1ogvb.jpg\" alt=\"better_error_resolver.jpg\">\u003Ch3>\u003Cstrong>Error codes are not just about errors, they are about experience\u003C/strong>\u003C/h3>\u003Cp>\u003C/p>\u003Cp>Error codes are often misunderstood as an after-the-fact firefighting tool, but in reality their effect on user experience is often more direct.\u003Cbr class=\"hard-break\">\u003C/p>\u003Cp>An error message, by nature, is only \"for people to read\", while an error code is \"a semantic signal for the system to use\".\u003C/p>\u003Cp>\u003C/p>\u003Cp>When errors are expressed as structured information, the front end and the flow design have more options. They can offer guidance that fits each situation,\u003C/p>\u003Cp>rather than just showing a line of error text.\u003C/p>\u003Cp>\u003Cbr class=\"hard-break\">From a product experience point of view, a system that only has error messages usually hands the job of understanding and fixing the problem back to the user.\u003C/p>\u003Cp>Think about it: would you rather the system showed you the usual toast saying \"Error while saving!\"?\u003Cbr class=\"hard-break\">\u003Cbr class=\"hard-break\">Or a guided dialog telling you that you do not have permission to edit and save this document, and what you can do about it?\u003Cbr class=\"hard-break\">\u003Cbr class=\"hard-break\">\u003Cbr class=\"hard-break\">Users usually leave without saying anything. Paying attention to every detail that might affect the user experience is what makes a product win.\u003C/p>\u003Chr>\u003Ch3>\u003Cstrong>Conclusion\u003C/strong>\u003C/h3>\u003Cp>A mature system is not one with fewer errors. It is one where, before errors happen, the team has already worked out how to deal with them.\u003Cbr class=\"hard-break\">\u003C/p>\u003Cp>And error codes are one of the most concrete, and most overlooked, expressions of that maturity.\u003C/p>","https://cdn.sqa.tw/blog_pictures/error_code.jpg","2025-12-21T05:16:00+00:00",true,"published","sqa","Error Code,software quality,SQA,software quality maturity,error handling design,Error Handling,system design quality,software architecture,QA quality indicators,how to assess software quality","Error codes are more than an error-handling tool. They signal software quality maturity. An SQA view of how they affect diagnosis, teamwork and user experience.",null,"2025-12-23T15:01:52.865+00:00",[19,26,32],{"id":20,"slug":20,"title":21,"excerpt":22,"image":23,"date":24,"category":25},"ai-development-sdlc-release-verification","When AI builds it in two hours but verification still takes three days","Once AI speeds up development, spec sign-off, testing and release do not automatically speed up with it. Using a real case from a booking system SaaS, we describe how we adjusted the SDLC to cut full release verification from two or three days to under two hours, and how the SQA role changed along the way.","https://cdn.sqa.tw/articles/ai-sdlc-verification-bottleneck-cover.jpg","2026-11-05T12:00:00+08:00","perspective",{"id":27,"slug":27,"title":28,"excerpt":29,"image":30,"date":31,"category":25},"sme-guide-to-choosing-ai-agent","AI agents are everywhere. How should a small business choose one?","We were recently asked to run a full post-deployment review of an AI agent, and found it had quietly caused five times too much raw material to be ordered from customer order emails, and nearly created a liquidity risk on the finance side. The problem with agents is rarely that they are not smart enough. It is that nobody asked the right questions.","https://cdn.sqa.tw/articles/sme-agent-black-box-inspection.jpg","2026-09-01T15:00:00+00:00",{"id":33,"slug":33,"title":34,"excerpt":35,"image":36,"date":37,"category":25},"ai-coding-team-collaboration-three-patterns","Three patterns we see once AI coding reaches the team","After working with more than ten development teams over the past six months, we keep seeing the same thing: individuals getting faster with AI does not mean the team is ready to get faster together.","/images/blog/ai-coding-teams-editorial.jpg","2026-08-20T08:00:00+00:00",{"slug":39,"title":40,"date":41},"qaptly-product-journey","Qaptly is here!","2025-11-13T15:35:00+00:00",{"slug":43,"title":44,"date":45},"upp-natural-language-iot-testing","When software testing meets the real world","2026-02-01T04:30:00+00:00",[47,48],"en","zh",1794970112952]