Gustav Brock
Gustav at cactus.dk
Fri Jun 27 02:12:51 CDT 2008
Hi Shamil Of course - and don't use dirty language. Quite a few comments to that article. This one from Solomon Grundy I like: <quote> Comments are just as important as the code itself. Otherwise you get what I call the 'Stonehenge' effect: in years to come no one will remember how to use it, or even what it does. Resulting in some coder saying, well, we just have to start all over again because this doesn't make any sense. (sort of like extreme coding, haha) The projects I lead are not complete until they are fully commented. Comments are part of the developers job, and if they can't get them done in a normal working day, that's too bad - they're either working late or taking it home. </quote> /gustav >>> shamil at smsconsulting.spb.ru 27-06-2008 01:34 >>> "Just don't overdo the comments, as comments must be maintained along with the code." http://www.theregister.co.uk/2008/03/28/case_for_comments_code/ -- Shamil -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Friday, June 27, 2008 3:17 AM To: Discussion concerning Visual Basic and related programming issues. Subject: Re: [dba-VB] Getting TextReader from strings... Uh, isn't that why they invented *comments*? Properly commented geek code isn't any harder to understand later than properly commented MMW code. It's the totally undocumented stuff that makes you think of changing careers, regardless of how it's written. Charlotte Foust -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Thursday, June 26, 2008 3:33 PM To: Discussion concerning Visual Basic and related programming issues. Subject: Re: [dba-VB] Getting TextReader from strings... Even worse is when you get called back to modify the project two years later and have to try and work out what you did all that time ago :-( On 26 Jun 2008 at 18:30, Gustav Brock wrote: > simply doesn't pay off. One example is that - most of us, I guess - > often copy snippets of code from one project to another to reuse not > as is but as a skeleton for something similar. If you have to spend > several minutes just figuring out how your original code works, you > are wasting your time. The real lesson is when you after many minutes > still can't find out - that's when I stopped playing smart.