From Name:
From Email:
To Name:
To Email:

Optional Message:


Why you shouldn't comment (or document) code

from Visual Studio Magazine

Comments should explain the "why" of the code and stop there. A great comment explains what purpose the developer felt that method or class should fulfill. That comment could be extended to include a description of how inputs and outputs of a method are related, and a list of expected side effects. But that's as far as any comment should go. more


Powered by MultiBriefs
7701 Las Colinas Blvd., Ste. 800, Irving, TX 75063