“Magic Strings” are Not So Magic
Error messages need to be clear and understandable not only for the Developer during coding but for the End User who is viewing the User Interface Messages.
Most Error and Information Messages go through an “Iteration Phase”
The “First Stage” messages may not be the “Final Stage” messages.
QA Team Members, Business Stakeholders and Pilot End Users will have input to the final version of Error and Information Messages
“Magic Strings” Used in Code for Messages Violate the Open/Closed Principle
The containing Class must be opened in the Visual Studio solution, the Message updated, the solution recompiled and then re-released to QA and other environments before final Production release.
An Enterprise Assembly Messaging System Complies with Best Practices
The Enterprise Messaging System process allows Messages to be Abstracted to the Database Layer rather than the Solution Code Layers
The Modern Developer’s Enterprise Messaging System
The following two tabs change content below.
I am a Principal Architect at Liquid Hub in the Philadelphia area specializing in Agile Practices as a Certified Scrum Master (CSM). I use Test Driven Development (TDD) and Acceptance Test Driven Development (ATDD) with Behavior Driven Development (BDD) as my bridge to Agile User Stories Acceptance Criteria in a Domain Driven Design (DDD) implementing true RESTful services