Don’t just use patterns & practices, build it!

You've used the blocks.  You've read the guides.  Maybe you've wondered where they come from?  Maybe you've thought you could do it better? Now, come to Redmond and show us how it is done.  The patterns & practices developer team is looking for top developers around to keep raising the bar on the stuff we product.  With our quick product development cycles, you'll get a wide variety of projects and help Microsoft’s customers develop sophisticated applications and achieve more predictable results. I've been in the group for 3.5 years and it's been quite a learning experience. 

Jim Newkirk has a post on his blog for anyone interesting in taking on an exciting challenge.

{Dr.Dre - The Chronic}

Comments (2)

  1. I’ve read a lot about patterns and practices, both within Microsoft and other communities. I still am wondering, how does the patterns and practices team relate to the group. Does the patterns and practices team communicatie with the Platform Architecture Group? Is it different than guidance?

    Maarten Strobosch

  2. Sandy says:

    The patterns & practices team is also known as the Platform Architecture Guidance team (PAG). Since we’ve taken on the patterns & practices moniker a couple of years ago, we’ve tried to avoid using the PAG name to not cause confusion. There is also the Architecture Strategy Team (formerly known as .NEAT) that we work closely with, but there is technically no "Platform Architecture Group". For patterns & practices and PAG, it’s all about the guidance. Hope that helps.

Skip to main content