Are we Delivering Enough Quality Worth of the Money we are Getting in Reward? This is a question by Raymond Lewallen (an active architect of Microsoft platform– though some JAVA-Lovers may ask a question whether there are any architects on Microsoft technologies). He argues that a lot of developers are delivering less maintainable and less robust code and getting fat pay checks for that and the industry should do something to change this pattern.
Full at: There is too much money to be made in software development – Raymond Lewallen http://codebetter.com/blogs/raymond.lewallen/archive/2008/01/22/there-is-too-much-money-to-be-made-in-software-development.aspx
Filed under: Uncategorized |
SIDQ-log (صدق لاگ) - Shahid Siddiqui's blog 
Businesses pay for quick hack jobs because time-to-market and short-term results are more important to these businesses.
In the end ‘maintainability’ and ‘robustness’ are trade-off issues. Recall the following well-known tradeoffs:
1- Budget, Scope, Time, Quality (Any project)
2- Speed, Space and Error (Algorithm design)
If readers are surprised by (2), I want to refer them to primality testing. Error free algorithms are intractable for large numbers so most people use randomized algorithms (e.g. Miller-Rabin) with a small chance of error.
So returning to the original theme … you could try to ‘change this pattern’ if you mean lessen the number of hack jobs but it will be impossible to completely eliminate it.