Brendan, Hi. Totally agree with all of your post and its sentiments...I've spent years maintaining other developer's code (mostly 4D up until the last couple of years) and most of what I've come across sucks from a maintainability angle (poor variable naming, no code comments, methods with excessive code, etc.)...the neglect and shortsight that most code is written with is a joke...so called 'smart' programmers such as those employed by financial institutions are the worst cuplrits in my experience...
Regards, Narinder. -- ___________________________________________ | Narinder Chandi, | ToolBox Systems Limited, | Surrey, England, UK. | http://www.toolbox.uk.com |___________________________________________ | Consultancy * Development * Support | * REALbasic Developer Program Member * |___________________________________________ on 1/5/07 15:50, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote: > This whole discussion misses the point. Maintenance of the code > "trumps" all the merits of putting DIM statements in any > other place but the top of the method since putting DIM statements > within the code are negligible at best. If you scatter your DIM > statements within your code you make your code harder to read. > Which is more important, your time as a developer or some > negligible benefit? If your time is only worth $1 an hour, then > have at it an write unmaintainable code, but the professional > developers typically earns $50 or more an hour and making your > code harder to read is rather short sighted. > > RB Code Reports is about enforcing the process of creating > maintainable code. RB Code Reports is not for you if you intend to > be a cowboy programmer. Some of you may take offense at that > statement thinking I am dumping on your poor coding practices you > consider just fine, but you need to recognize the reality of what > you are doing. As I look out over the the code put out by the RB > community, very little of it could be considered maintainable. To > be blunt, a lot of it is crap. This in not a unique characteristic > of the RB community itself, but programmers in general. There is a > blatant disregard to make code maintainable because it takes more > effort to do so and it is a choice made out a lack of attention to > detail. There are decades of common experience of dealing with > unmaintainable code and people continue to choose to repeat the > same mistakes over and over in spite of knowing the cost they will > pay down the road. Is this not the definition of stupidity? _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
