Today we are packing for the big move. Quick Solutions is moving to some new swanky office space, with an awesome new delivery center. The new center has wall to wall whiteboards, network projectors for group programming (pair programming is so 20th century), a game room, new open seating (shared workspace is the key to productivity), and lots of other new goodies. It is an amazing investment by the company, and shows their commitment to building the best team on the block.
As we are packing, we started joking around (not that joking around is rare, and would have occurred regardless of the packing state). How does and architect pack? An architect doesn't pack anymore. He did that ten years ago. He goes to plenty of packing conferences, and has read a lot of books on packing. An architect will map out how the whole enterprise should pack, and even dictate what (clearly out of date) packing supplies and processes should be used. These processes will be the perfect match for some scenarios, but not all, but will ruthlessly be applied to all anyway. The architect will require team reviews of the packed boxes, and find ways you could have done it better (without regard to time or resources). He will spend months developing gigantic packing diagrams, and box flow-steams using the latest UML tools. All of which will be out of date before they are ever published.
All in jest of course.
Link back here with your response:
- Alexei, how does a TFS geek pack?
- Jim Holmes, how does a tools nerd pack?
- Bruce, how does a data architect pack?
- Monish/Arnulfo, how does a BizTalk guy pack?
- Wingfield, how does an ajax guy pack?
- Jeff, how does a siliverlight guy pack?
- Phil, how does a MOSS guy pack?
- Randall Drum, how does a PM pack?
- Steve Harman, how does a framework guy pack?
- How does an open source guy pack?
- Josh, how does a Web 2.0 guy pack?
- Bender, how does a WCF'er pack?