On Thu, Nov 20, 2008 at 6:33 PM, Andrew Farnsworth <[EMAIL PROTECTED]>wrote:
> This is exactly the reason that I push maintainable code over efficient > code (ok, overly optimized code). It may take you a week to write it, but > it has to be maintained for years afterwards. This basically means don't > use obfuscated code or what could be perceived that way by almost any > moderately competent programmer. > > Just keep it simple and only optimize your code where it can be proved to > be a perceivable improvement. If possible or necessary, move the processing > offline and give the end user a "Still processing" screen until it > completes. > > This does not mean you should write code that is manifestly inefficient > just to write inefficient code. Find that happy medium but keep in mind > that someone else will be maintaining it, and tomorrow you will be > maintaining their code. > > Preemptive strike here. Yes, I know there are situations where you really need to optimize code, such as low level hardware drivers, database store procedures, etc. However, the vast majority of code is not in this category and should be written to be as maintainable as possible. Even highly optimized code should be very very well documented, even to the point of providing a non-optimized version that is easy to understand. Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en -~----------~----~----~----~------~----~------~--~---
