Comments on: Intellisense Driven API Design

By: Gibraltar 2.1.1 Released :: Rock Solid

Gibraltar 2.1.1 Released :: Rock Solid — Fri, 19 Feb 2010 05:49:00 +0000

[...] most important. Are we missing something you need? Let us know: we’ve proven we listen again and again and [...]

By: Managed Thread Ids – Unique Id’s that aren’t Unique :: Rock Solid

Tue, 16 Feb 2010 06:08:16 +0000

[...] The frustrating part is that if the documentation had never made any claim about the uniqueness of the thread Id we’d likely have gone through a set of proof and qualification testing. Like many people, when there isn’t documentation on something we have to create experiments to tease out the true behavior, review source code, and then decide what risks we want to take. This is one reason we are passionate about documentation, even at the expense of extra features. We want to make sure that you never have a doubt about what something on our API does. We also know that people don’t want to review documentation if they don’t have to – so we try hard to make the API understandable just from Intellisense. [...]

By: Alex James

Alex James — Sun, 03 May 2009 05:30:12 +0000

Nice article.

I’ve been thinking for a while about honing the developers intellisense experience of an API, even little things can have an interesting impact see this:

http://blogs.msdn.com/alexj/archive/2008/04/09/intellisense-what-properties-are-required.aspx

By: Jason Short

Jason Short — Wed, 29 Apr 2009 16:44:09 +0000

Great article. I do feel that Intellisense Drives most programmers today. Having less exposed is much more intuitive and results in an easier to learn experience for programmers.

The old saying that “less is more” definitely fits here. I like what you guys did. The classes feel much more flushed out because each one seems to have an obvious use.