On Oct 30, 2013, at 2:47 PM, Stephen Russell <[email protected]> wrote:
> http://visualstudiomagazine.com/articles/2013/06/01/roc-rocks.aspx > > Article is Why You Shouldn't Comment (or Document) Code Geez, I keep seeing this same tired argument, especially from the Ruby crowd. Yes, stupid comments should not be in your code. You should choose your names to indicate what the code does. Your comments should be for the edge cases where the expected behavior is not desired, for whatever reason that might be. You can save your successors a great deal of grief with a simple note as to why the obvious road was not taken; you simply cannot do that with a test. -- Ed Leafe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
