Geeks With Blogs
John Smith's Blog Keeping the fun machine running one nickel at a time

I had the opportunity to return to the Patterns and Practices Summit this year for the second time.  The first time was in 2008, and they managed to plus that experience this year.

 

All of the technology was on track, and par, for what Microsoft has been pushing toward us  - 2010 being a huge year for major releases as well as out of band stuff.  The presenters did an awesome job presenting and here are/were my favorites for this year.

 

Monday azurethumb(Workshops)

Azure (@ScottDensmore, Eugenio Pace (think Pa-ch`ay) and how they covered the different ways the cloud can be used (SQL, Storage, and Apps).   I had a block on how all of this stuff actually locked arms, and now its clear how to position (and build) a solution with all that Azure offers.

The HOLs on Monday drove a lot of value to understanding the platform and also built a base for the Azure talks during the rest of the week.  There was a fair amount of Claims-Based Identity baked into this talk as well.  Something that can help any with authentication, on the dev and app fabrics

 

That was Monday, deep-dive on Azure.  The other two HOLs given that day were on Enterprise Library 5.0 and Patterns for Loose Coupling aka Prism.

 

Tuesday (MishMash Day : Craftsmanship, DI/IoC, Users’ Needs, Parallel Programming, Arch Katas)

Keynote from “Uncle” Bob Martin: Bob just basically told us how poor process and coding were helping us to write code that sucked.  And basically his charge was that it didn’t have to.  Bob is a big proponent of using tests (using whatever kind of xDD) to start the documentation process early.  Some of his talked is echoed from “Clean Code”, but most of it was a alarm that we should be thinking more about what we are building not so much on how we’re going to build it.

 

Hammet Verissimo & Michael Puleio: DI / IoC

Dependency Injection and Inversion of Control are two patterns.  Start there.  Using these patterns along with other frameworks is not DI and/or IoC.  I thought I was very clear on these two topics since we used them a lot already, but they helped clarify more so of why we use them.

 

David Platt “The Quadrant of Ubiquity”

Imagine a square divided into four equal parts.  The left axis “X” is used to determine how deep the user will use the application;  the “Y” axis will determine how much the user will use the application.  This helps define where to put which features for an application.  As an example, think about two very different apps, WinZip and Word.  How much deeper do you go into each app for features?  How much do you use each feature.

 

Ade Miller - Parallel Programming

It’s not as easy as just using the PLinq extensions to access one of the other cores on your desktop or application server.  It take a bit more thought.  The idea is to not think of everything as a nail b/c you have a giant freakin’ hammer like parallelism to work with.  Ade explained there are other ways to use the Parallel library to affect data and task parallelism, and Aggregation, Futures, and Pipelines.  Great, deep talk on this.

 

Ted Neward - Architectural Katas

The whole group was split up into teams of 4-6 tablemates to solve a problem and determine an architecture for a random problem that was handed off to each team.  Our table had a World of Webcraft game to build; others were public/private school administion software, and an internet ice cream selling site.  When we finished with our high-level architectures we discussed (and defended) them to the rest of the group.  Not one of the teams considered how the solution would have been tested.  That was my takeaway, as it was for others. So busy figuring out what to build we had already forgotten how to test it.

Posted on Sunday, October 24, 2010 4:19 AM .net | Back to top


Comments on this post: Patterns and Practices Summit 2010 (Monday & Tuesday)

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © onefloridacoder | Powered by: GeeksWithBlogs.net