|
>> BTW, I think in business programming (from the management/end user point >> of view) the first criterion is usually does it work? The second is how >> fast can you write it? Good program design isn't even a nice to have. >> If you need to take longer to design a good program than to slap >> something together that will work You know the silly thing is that writing good code is faster than writing bad code. Breaking things down into small pieces makes it easier to code, not harder and that, on the average, 70% of the work on a piece of code is going to be in maintenance. Writing unstructured monolith code just ends up taking more time. If you apply that to unnormalized databases and the time difference is unreal.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
