All software developers have been there.  You’ve started a new job, inherited legacy code, or been chosen to support an application for which you have not written a single line of code.  You spend hours perusing the code, trying your best to interpret the brain patterns of another developer, as laid out in source code.  “What were they thinking?”  “Why did they use a property there instead of a method?”  “What the heck does this ‘RunProcess’ method do?”  “What is this ‘aXList’ variable used for?”  It is under these conditions that you really begin to see the importance of maintainable code.  Or, consider an even simpler scenario, where you are the developer and the maintainer.  I’m sure I’m not the only one who has looked at my code a month or two after writing it, and not even realized that I had authored it.  When this happens, you’ll be glad you wrote your application in such a way that it is easily understood. 

Read more in the following whitepaper...

WhitePaper-SoftwareMaintainability.docx (138.87 kb)