I’ll take even the smallest evidence of success

I have made it my mission to institutionalize the value good API design.  I strongly believe that this is key to making developers more productive and happy on our platform.   One very small way to measure that success is to notice where 3rd parties have internalized that message, followed our guidance and use that fact as a selling point for why their product is better.  Someone just forwarded me just such a site: http://www.extremeoptimization.com/Mathematics/Usability.aspx… Here is a sample:


Consistency both with Microsoft’s Design Guidelines for Class Library Developers and internally, ensures that you can reuse what you have learnt building applications for the .NET framework.

 Do you know anyone else doing the same thing? 

Comments (10)

  1. We are following your Design Guidelines when we are building our classes. It’s important to have a naming guideline to follow so everyone in a company writes code in a similar way; it would make the code more readable for others.

  2. We promote our consistency with the design guidelines as a selling point. We do not have it on our website, but now that you mention it… we will add it!

    here is a mention:


  3. By the way, it is thanks to the FxCop tool we were able to be consistent. Our API was already thousands of members before we made our first release. There is no way we could have found all design guideline violations without FxCop.

  4. I’ve been peddling (not to mention following) these guidelines since 1.0 beta. On the C# forum of http://www.codeproject.com it always pains me to see "CMyClass" or "propertyName" (what is this, Java?). Consistency is indeed important for RAD, but you would think people would notice as they use all those classes, members, etc.

  5. http://www.vgdotnet.com/features.shtml

    Now mentions consistency with design guidelines.

  6. Jeff Parker says:

    I follow the MS design Guidelines, for 2 reasons

    1. They are great detailed guidlines. I have been following them and the Patterns and Practices.

    2. Saved me a hell of a lot of time writing guidlines for Sarbanes Oxley, I simply say we follow the MS Design Guidlines, go look them up and here is an FX Cop report.

    So thanks Microsoft most people don’t realize the Self Documenting C# Code Comments, tools like FXCop, NDoc, NUnit and Source Monitor has not only improved the quality of code, but it also helps get through things like Sarbanes and so on. That is one thing you never see published or talked about anywhere. You see Yeah .net is more productive, and yes when compairing writing code. But when you add in things like Building Documentation, and I mean Good Documentation, Sarbanes Compliance, and things like that. Even though I know those weren’t the intentions of .net but they are pleasant side effects.

  7. Yes, I like your guidelines and have been utilizing them and recommending them for a long time now. In addition to being good, there is the added benefit of your making them an industry standard and thereby lowering the learning curve. Thanks!