tag:blogger.com,1999:blog-6691579676571716537.post5976631225433655123..comments2023-07-02T10:08:07.024+01:00Comments on Project 20: "How to Keep Your Code From Destroying You"...or notIan Dykeshttp://www.blogger.com/profile/08235675789374664427noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6691579676571716537.post-40718186248306515012007-06-05T12:34:00.000+01:002007-06-05T12:34:00.000+01:00Working with Ian at Esendex i whole heartedly agre...Working with Ian at Esendex i whole heartedly agree that we don't need to comment our code too much, at least for the most part. The only real point i'd like to add is if you feel that it really is neccessary to comment a method decleration then use XML comments /// so that people can read the comment using intellisense. The comment will pop up whenever the method is being used in code which is the only reason i can think of to comment a method. If the user has opened the code to take a look at what the method does then, as previously said, the method code should be self explanatory but an XML comment can save you going to have a look at what the method is doing.Kevin Pearmanhttps://www.blogger.com/profile/09203340764000599358noreply@blogger.com