Agile 2011 - Day 4-5

Thursday I went to WIP and Kaizen: Key Tools for Enabling Continuous Improvement: Michael DePaoli. It was a really interesting talk about how you need to make change slowly, incrementally and steadily to arrive at the organizational goal without causing a fight or flight reaction in your people. I enjoyed it though I expected it to be more about personal improvement for some reason.

I wasn't really excited about any of the late morning sessions, so I bailed and went to Coach's Corner to hang out with Tim Ottinger and ended up meeting Colin Jones from 8th Light and then talking with Matt Barcomb from LeanDog for nearly an hour.

Around noon, Evana Fredricko, my dance partner for Brian Marick's session on Tango, The Stance of Reaction, and Pair Programming arrived. We went out for a slice of pizza near the hotel, then returned for a very fun intro to tango and a great discussion on paired programming. A correlation was drawn between the way dance is taught and the way we should teach software practices: demonstrate, practice in isolation, then practice in the full context of dancing/working.

After thanking Evana for her time, I returned late to the hotel so I missed How Functional Programming Changes Developer Practices and went to The Fundamental Agile Apologetic: Tim Ottinger instead. I chatted with Tim and Rachael Davies about how the constraints of an average software project will lead you toward a set of practices similar to those of XP or other agile methodologies.

The Open Jam was pretty crowded so I wandered around the quiet halls until I found an ex-coworker. We talked shop and how things were going at his company. All too soon, the end-of-conference party started and I went around and said goodbye to my new friends and went home early.

Friday, Dave Brady carpooled to the conference with me. We both really enjoyed Kevlin Henney and Linda Rising's talks and spent some time talking to them after. From there, we went back to the Open Jam to hang out with GeePawHill, Tim Ottinger and Angela Harms. Tim and I left for a late lunch and I dropped him off at the airport.

I am now exhausted and yet completely energized. This was an amazing week full of learning and friendship.

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