Agile 2011 - Day 1

Holy shit! The internet isn't just a series of tubes, it's real! This may affect the way I interact in here... ;-) Anyway, I actually got to meet and shake hands with so many amazing people today including: Michael Feathers, Bob Martin, Angela Harms, Michael Hill, Tim Ottinger, Jeff Langr, Martin Fowler. My mind is nearly blown. There is so much talent and experience here I almost can't believe it.

The Plan:
Attend Refactoring in the 4th Dimension: Michael Feathers in the morning and The Transformation Priority Premise: Robert Martin in the afternoon.

Actual:
The Refactoring session was really interesting. Thinking about how your code base evolves as opposed to just looking at a point in time leads to some interesting metrics. A lot of research needs to be done in this area. Also, my Ruby skills are teh suck. I really need to practice and build a nice breakable toy.

Lunch was better than I expected and worth the wait. The highlight was a brief conversation with Angela Harms and Micheal Hill. I ate with a random attendee whose name I have forgotten.

The afternoon session with Uncle Bob was everything I expected. It was entertaining and educational I ended up pairing on the samples with the same guy I met at lunch. If you weren't able to make the session, it was a longer, hands-on version of his NDC 2011 talk.

After that we had there was a humorous and informative Q&A session with 15 of the original 17 authors of the manifesto.

The day ended with the Ice Breaker event with had amazing food and the opportunity to chat with several of the presenters I am so excited to see this week.

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