Craig has some great reviews of the recent DevLinks days in his area but this post caught my eye: DevBlog: DevLink Day 2 Why? Two reasons: 1) This comment: "Concepts such as what kinds of comments and how many are important. It turns out that most comments in code aren't needed. If you write self-documenting code, even fewer are needed." Those who attended my sessions at last year's SWFox heard me state this numerous times in my session on Code Analyst - even to the point where it appeared I was suggesting getting rid of comments entirely. In a recent project, though, it became even clearer - I only needed comments to bookmark where I may need to do future work. Self-documenting code is essential to maintainable code - and while having methods like GetPubishingAcronymForABookTitle goes into overkill of how to name a method, naming your methods right is important regardless of the language. On the other side of the coin, one of the tools used in a recent project was a
Solutions for Today; Ready for Tomorrow. Andrew MacNeill's blog about development, technology, Visual FoxPro, databases, community and occasionally, some off-topic discussions.