.NET Coding Guidelines - Commenting
posted by dwhittaker(13.1k) 4 years, 9 months ago 0
Commenting for the sake of commenting is poor, however, commenting on the intent is a MUST. Simple easy to read code should not need comments. However, code the is odd/complex or is a 'hack' MUST have comments so the next guy can understand the 'intent/why' of what the code does.
Reply
Sam Gentile: Goodbye CodeBetter and ALT.NET
posted by dwhittaker(13.1k) 4 years, 7 months ago 0
I think you got your description of the post wrong. It is not CodeBetter that is Anti-MS, it is Sam that has been speaking out lately about MS.....
Introduction to the AutoMocking Conatiner in StructureMap
posted by dwhittaker(13.1k) 3 years, 6 months ago 0
@Birdchest, I am sure Jeremy (author of SM) would be happy to accept a patch for unity if you wanted to submit one.
DNK Community Guidelines - Suggestions welcome!
posted by dwhittaker(13.1k) 3 years, 5 months ago 0
Put this set of rules/guidelines someplace on the site that is permanent so ALL posters know what is allowed and what is not forever.
Working With ASP.Net MVC Part 2 - The Model And The Repository Pattern
You name the post Asp.Net MVC then never talk about MVC, then at the end you say 'Again we didn’t really look at ASP.Net MVC. Don’t be angry.'. Name the post so it conveys the actual content of the post. Putting a fake name on the post to get hits is sad, just sad.
Learning to use Fluent NHibernate: Getting started w/ your 1st Mapping
posted by dwhittaker(13.1k) 3 years, 3 months ago 0
wow, pretty easy to say something is pretty bad with nothing behind it. If you did not like it why? Did it not show you how to map a few tables? Did it not explain things clearly?