Comments for chris clarke http://squadlimber.com/chris software development that works...or something Thu, 28 Aug 2008 10:37:05 +0000 http://wordpress.org/?v=2.0.5 Comment on Ignoring Common Coding Practice (why you should be too) by Brian Marick http://squadlimber.com/chris/2008/04/04/ignoring-common-coding-practice-why-you-should-be-too/#comment-6347 Sun, 06 Apr 2008 15:12:16 +0000 http://squadlimber.com/chris/2008/04/04/ignoring-common-coding-practice-why-you-should-be-too/#comment-6347 Looking forward to the day when those are common practices people start to question... Looking forward to the day when those are common practices people start to question…

]]> Comment on Continuous Deployment by chris clarke » Continuous Deployment As A Practice http://squadlimber.com/chris/2006/12/16/continuous-deployment/#comment-378 Sat, 26 May 2007 12:51:21 +0000 http://squadlimber.com/chris/2006/12/16/continuous-deployment/#comment-378 [...] A lot of people do Continuous Integration these days (even if that just means source control and CruiseControl). But very few teams seem to do any form of Continuous Deployment. The point of Continuous Integration is to detect integration problems as quickly as possible and to reduce the risks involved in a deferred integration. A deferred integration is something that will delay the release and may take an unknown amount of time and involve an unknown amount of problems. As Martin Fowler says in his article: “you are putting yourself into a complete blind spot right at one of tensest parts of a project” [...] […] A lot of people do Continuous Integration these days (even if that just means source control and CruiseControl). But very few teams seem to do any form of Continuous Deployment. The point of Continuous Integration is to detect integration problems as quickly as possible and to reduce the risks involved in a deferred integration. A deferred integration is something that will delay the release and may take an unknown amount of time and involve an unknown amount of problems. As Martin Fowler says in his article: “you are putting yourself into a complete blind spot right at one of tensest parts of a project” […]

]]> Comment on Annoying Patterns: The Hidden ‘On’ Switch by Duncan Pierce http://squadlimber.com/chris/2007/03/15/anti-patterns-the-hidden-on-switch/#comment-6 Fri, 06 Apr 2007 13:42:24 +0000 http://squadlimber.com/chris/2007/03/15/anti-patterns-the-hidden-on-switch/#comment-6 Yep, this kind of thing is really irritating. Sometimes you feel like there's a whole hidden state machine in there. <code> api.doStuff(1); api.doStuff(2); Exception: doStuff(1) called without init() api.init(); api.doStuff(1); api.doStuff(2); Exception: doStuff(2) called without finish() api.init(); api.doStuff(1); api.finish(); api.doStuff(2); // aargh - should there be a finish() here? } </code> If the code is able to validate its own state it ought to be able to manage it for you too. The fact that it can't is usually down to poor API design: they often carry too much state. Yep, this kind of thing is really irritating. Sometimes you feel like there’s a whole hidden state machine in there.


api.doStuff(1);
api.doStuff(2);

Exception: doStuff(1) called without init()

api.init();
api.doStuff(1);
api.doStuff(2);

Exception: doStuff(2) called without finish()

api.init();
api.doStuff(1);
api.finish();
api.doStuff(2);
// aargh - should there be a finish() here?
}

If the code is able to validate its own state it ought to be able to manage it for you too. The fact that it can’t is usually down to poor API design: they often carry too much state.

]]> Comment on Retrospective: Storyboard by chris clarke » Unit Tests In Javascript http://squadlimber.com/chris/2007/01/11/retrospective-storyboard/#comment-5 Fri, 02 Feb 2007 01:34:43 +0000 http://squadlimber.com/chris/2007/01/11/retrospective-storyboard/#comment-5 [...] Looking around for AJAX libraries to use for storyboard following a retrospective around the initial development, I stumbled across scriptaculous, one of the benefits being that it has it’s own unit test library. An alternative may be to use jsUnit which has syntax much more familiar to anyone who’s ever used JUnit. [...] […] Looking around for AJAX libraries to use for storyboard following a retrospective around the initial development, I stumbled across scriptaculous, one of the benefits being that it has it’s own unit test library. An alternative may be to use jsUnit which has syntax much more familiar to anyone who’s ever used JUnit. […]

]]> Comment on Continuous Deployment by chris.probably http://squadlimber.com/chris/2006/12/16/continuous-deployment/#comment-2 Sat, 16 Dec 2006 08:51:50 +0000 http://squadlimber.com/chris/2006/12/16/continuous-deployment/#comment-2 I re-read this and realized that I missed a trick, surely a Continuous Deployment server should continually take the last successful build and deploy it to a ready-to-go live system. It should then be possible to switch from old to new with no downtime.  Build, deploy and release at the flick of a switch. I re-read this and realized that I missed a trick, surely a Continuous Deployment server should continually take the last successful build and deploy it to a ready-to-go live system. It should then be possible to switch from old to new with no downtime.  Build, deploy and release at the flick of a switch.

]]>