If Adam Cogan made a movie…

I was sitting with my family this weekend watching the movie Zombieland.  The film begins with a narrator discussing how a “… zombie apocalypse has been triggered when mad cow disease became mad human disease and then worse”.  During the course of the film the main character lists out his “rules for surviving Zombieland”.  My first thought was “Wow…Adam Cogan must have written this film”.

If you don’t know, Adam has rules for pretty much everything so this is a natural fit.  I should ask him to complete the list for us.  ;-)

Here’s some screen caps that show why.  The full, incomplete list can be found here.

Rule 1: Cardio

Rule 2: Double Tap

Rule 4: Seatbelts

 

Technorati Tags: Zombieland,Adam cogan,Tongue in cheek

Submitted Sessions for New England Code Camp 13

I just finished submitting two sessions for New England Code Camp 13 on March 27, 2010. 

I’m planning on doing a session on moving teams from Visual SourceSafe to TFS 2010 and a session on solving the “No Repro” issue with the tools in VSTS 2010.  You can see the presentation summaries and signup at TheDevCommunity.org

Looking forward to seeing lots of people in these sessions.  There some really cool stuff in here.

- Steve

Technorati Tags: New England,Speaking,Code Camp,TFS 2010

Teamprise Build Extensions for TFS 2010 RC

[UPDATED 4/24/2010 – Microsoft has released the RTM version of these Build Extensions.  Please see this post.]

In a prior post, I posted the code and binaries for an updated version of the Teamprise Build Extensions that works with TFS 2010.  At the time it was compile against TFS 2010 Beta 2. 

When the TFS 2010 RC was released a breaking change was introduced in the TFS API.  This updated version of the Teamprise Build Extensions works with the RC.  Hopefully, it will also work with the RTM version when it is released.  I’ll post back here to let you know when RTM ships.  

As before, at some point there will be an “official” release from the Teamprise team at Microsoft.  When that happens, I’ll deprecate these 2 posts and point them to the official code.

The Teamprise Build Extensions are licensed under the Microsoft Public License (Ms-PL).  This license pretty much says that you can make any changes that you like.  Thank you Teamprise!

All the usual disclaimers apply…I won’t be held responsible for anything; good, bad or otherwise and this code is still published under the Ms-PL license.  ;-)   If you find any problems, please let me know and I’ll do my best to fix it.   

 
The zip file contains the source code, Debug build binaries and updates xslt.

To install:

1. Install the Teamprise Build Extensions for TFS 2008 found at http://labs.teamprise.com/build/extensions.html
2. Copy the DLLS and xslt directory from the \bin folder in the root of the zip file to C:\Program Files\MSBuild\Teamprise\v2.

- Steve

Technorati Tags: Teamprise,TFS 2010,TeamBuild

New England Code Camp 13 Announced…time to sign up!

Chris Bowen has formally announced the next installment in the Code Camp series…New England Code Camp 13 “Spring Back into Code”.

Date: Saturday, March 27, 2010
Place: Microsoft, 201 Jones Rd, Waltham, MA  Bing Maps
Cost: Free

Time to start thinking up presentations…maybe something on IntelliTrace in VS 2010.  Love IntelliTrace!!

Technorati Tags: Code Camp,Development,New England,Speaking

An excellent post about Developer Professionalism

I don’t normally write blog entries that say “Go look at this post by someone else”, but I am today.

Scott Bellware has written an excellent piece entitled “QA Missed Something”. 

“When a team is closing in on a release it may still find a flaw so terrible that the release opportunity might be missed. After the initial panic settles down, we go looking for the explanation of why a such a significant problem can remain hidden until so late. Inevitably, QA missed something.

Let me tell you something: there's nothing that QA has ever missed that developers didn't miss first.”    - Scott Bellware

I recommend that every developer out there reads this and takes it to heart.  We have way too many “unprofessional developers” in the world.  It’s time to get back to developer responsibility for their own code’s correctness. 

We are a Software Development Team.  If the software fails, the Team fails…period.