By Rob Park on
Sunday, March 22, 2009
Simple requires discipline and courage.
Just implementing some feature without tests and without really considering the class responsibilities involved… that’s easy… well for a little while anyway. However, being disciplined to test-drive your change in and then refactor mercilessly for single responsibility, removing duplication, etc that’s how you keep your design simple.
Just exposing your class’s data and then reaching into it further, violating the Law of Demeter, that’s easy. However, being disciplined to recognize you have some inappropriate touching going on and instead at least encapsulating that into tested methods will help keep your design simple.
Even then, if you do recognize for example a class is too big, just taking some of it (hopefully related pieces) and putting them in depe
Read More »
|
By Rob Park on
Saturday, March 14, 2009
I'm a consultant now...
Current gig: Flex/ActionScript front-end to RESTful Java back-end; back-end integration tests with Easyb; and a handful of issues (mostly related to Scrumbut) to keep me entertained.
And you can now find me on Twitter @robpark.
Read More »
|
By Rob Park on
Sunday, August 17, 2008
On our team, we are using Kanban-style queues to manage our story production. We count cycle time to be from the point it enters the queue (out of to do) to the point it leaves the queue (done-done). Currently, our average cycle time for stories is 15.7 days, which isn’t good especially considering we still track iterations as 2 weeks (10 days). So my entire focus at the moment is how to get our cycle time down.
Read More »
|
By Rob Park on
Saturday, August 09, 2008
Anything you want to discuss?
There are few articles from years past on http://www.agileskunkworks.org already.
I'm still using many of the same tools: NUnit, Spring Framework, Cruise Control, FitNesse, etc...
Send me an email at robert.d.park@gmail.com if there are any topics of interest to you.
Read More »
|