Maintanence of a crapy project

When a crap of web application is built, we can often hear WTF around office a lot. Generally, a web application does not end with a web developer, rather it start with him/her and will be used by bunch of user who does not care how it should work. To avoid these users to destroy a badly coded web application, CEOs came up with an idea of Code Review.

Code review, to a certain extend increases the quality of web application, but these reviews definitely test the patience of Software architect. And the below image would suggest, the number of WTF during this phase of implementation. I came across similar crap of the project few months back, where the code were all messed up, and so called MVC was MMVVVC.  And its not easy to maintain and enhance these projects. And at this stage, we have to make a decision of completely replacing it or enhancing it to the level we can. I would always prefer the first option, but the project manager would always prefer the later one. And the result is, one big mistake at the start of web application cost you double to maintain it and more than 400% to enhance anything on it.

 

Reference: http://wtfcode.net/post/187085474/the-obligatory-image-c-2008-focus-shift-osnews