RSS 2.0

Personal Info:

Joe Send mail to the author(s) leads the architecture of an experimental OS's developer platform, where he is also chief architect of its programming language. His current mission is to enable writing large-scale software that is reliable, secure, and scalable by-construction. Before this, Joe founded the Parallel Extensions to .NET project. He has been granted 19 patents, with 49 pending. When not working, Joe enjoys travelling with his wife, writing books, writing music, studying music theory & mathematics, and doing anything involving food & wine.

My books

My music

Disclaimer:
The content of this site are my own personal opinions and do not represent my employer's view in anyway.

© 2012, Joe Duffy

 
 Tuesday, December 21, 2004

Early last year, Brad, Krzystzof, Steven, Rico, and several other people put together a great internal training class on best practices for developing managed APIs. The course targeted primarily any PMs, developers, or testers that are actively building products that expose public APIs and run on the .NET Framework. It's also relevant to people who are designing for re-use within their own projects, even if they don't expose any APIs per se. It was a huge success here at Microsoft.

And, I'm pleased to let you know that we recorded the entire thing, did some editing and tweaks over the last months, and now it's ready to put into your hands!

Starting January 7th (Friday), we'll be posting this content up on MSDN, staggered over a period of time. We'll also be coordinating chats with the experts behind each session shortly following the posting of each video... you can ask questions or engage in conversation with the architects, developers, and PMs responsible for the class content. Frank's still putting together the concrete details, so I'm being intentionally somewhat vague. :)

The courses cover a lot of the material from the Design Guidelines document (plus some extra goodies), with ~1hr dedicated sessions on:

  • Naming conventions
  • API design basics
  • Usability
  • Designing for subclassing
  • Security
  • Performance
  • Designing in a managed memory world
  • Interop
  • Packaging and deployment
  • And a whole lot more!

I'll post more detailed information as the plans solidify.

Update: Brad posted a link to an older post where he details class topics a bit further.

 

Recent Entries:

Search:

Browse by Date:
<December 2004>
SunMonTueWedThuFriSat
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678

Browse by Category:

Notables: