Agile 2011 - Day 0

While there were no sessions, I think that the Agile 2011 conference technically started today. I was there anyway. Here is the report.

The Plan:
Head up to the Grand America for the 5:15 First Time Attendees session. Hang out until 7:00 then go over to the Zombie Walk.

Actual:
I went to SLC Airport to pick up Brian Marick and take him to the hotel at noon. He treated me to an excellent lunch at Squatters. I had the Black and Bleu burger which is at least as delicious as it sounds. While the food was great, the conversation was better. It was a wonderful opportunity for me to make the hang and learn directly from a well-known master. We spoke at length about software, languages, pets, programming jobs, XP, psychology and gift economies. It was an amazing lunch.
After dropping Brian off at his hotel, I didn't really have time to drive home and back before the 5:15 session, so I decided to wonder around the Grand America. Soon I was helping the volunteers sort shirts and prep welcome packets. After that, I went to the Agile Alliance lounge and hung out until the session.
I skipped the Zombie walk because I was missing Nikki and the kids and I know that, even as a local, I am going to be busy around the clock with the conference this week and I won't see them much. Spending time with them at the splash pad in The Ranches is more fun than hanging out with hipster zombies any day.

Comments

Post a Comment

Popular posts from this blog

TFS to SVN Conversion with History

Recently, the team I was on wanted to move our source code from Team Foundation Server to SVN for reasons that had almost nothing to do with source control directly. This would be a pretty simple operation, but we didn't want to lose access to the history when the operations team turned off the machine running TFS. We couldn't find any direct paths for moving history from TFS to SVN, so instead we chose to use git as an intermediary. Here's how we did it: Step 1 - Install the tools Install msysgit: http://code.google.com/p/msysgit/ Install git-tfs: https://github.com/git-tfs/git-tfs Step 2 - Pull TFS history to local git repository git tfs clone <tfs-project-url> "$/<tfs-project-name>/<tfs-project-folder>" <localfolder> example: git tfs clone http://tfs-001:8080/tfs/projectroot "$/Reference Architecture/ReferenceArchitecture" RefArch Step 3 - Initialize git-svn * User Lower Case - Caps will make it fail! * Change direc...
Read more

Simpler Tests: What kind of test are you writing?

One common problem that I see in test suites is confusion about what each test should cover. This confusion often leads to tests that are either too broad or too focused to accomplish the goal of the author. When writing a test, it is important to think about what kind of test it will be and the constraints that make that type of test effective. There are a few broad categories of tests that I keep in mind to help focus my testing: Unit Tests Also called micro tests, unit tests form the foundation of any good testing strategy. These are tests that test a single class or method in isolation from it's dependencies. Mocks and stubs help us isolate the code under test and make our tests more focused and expressive. A test that touches any external resource such as the database, the file system, a web service, etc is never a unit test. The primary purpose of unit tests is to validate that the subject under test is functionally correct for the expected inputs and outputs. Additiona...
Read more

Architecture at different levels of abstraction

Image
This week I am attending the O'Reilly Architecture Conference in NYC with my team and I had the pleasure of attending a two day training on Building Evolutionary Architectures presented by Neal Ford and Rebecca Parsons . During this session, on of the things we talked about extensively was coupling. We looked at dependency maps for different architectural styles including the big ball of mud . We saw something like the following and almost everyone agreed, "That is a bad architecture." Big Ball of Mud This reminded me of something I has seen elsewhere before, and after a quick search, I found it: Amazon and Netflix Death Star Architectures The ball of mud is considered obviously wrong by most architects, but the death star seems to be held up as an ideal by just as many and likely most of the same architects. Why is this? Are afferent coupling (inbound dependencies) and efferent coupling (outreaching dependencies) only important at a certain sc...
Read more