.NET Coding Guidelines - Commenting
posted by IDelectable(290) 4 years, 9 months ago 0
I agree to an extent, I'd usually rather have well designed self-documenting code than awful code that's commented. But, especially with larger and more complex systems, it good to have documentation and comments too, so you can tell what the programmer was trying to do, and why. There's a limit to what you can infer from code alone, no matter how well designed it is.
Reply
dwhittaker - I agree, for hacks it's handy to use "HACK" comment, same for "TODO", so they show up in the Visual Studio Task List.