Comments on: Done is really done http://www.nettpar.org.uk/2010/02/14/done-is-really-done/ Tue, 23 Aug 2011 20:35:16 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Phil Wilson http://www.nettpar.org.uk/2010/02/14/done-is-really-done/comment-page-1/#comment-340 Phil Wilson Fri, 14 May 2010 12:32:13 +0000 http://www.nettpar.org.uk/?p=343#comment-340 I like this quote under the heading "Antipatterns": "Partial delivery: not delivering into production. Unless delivering into production, "done" is more an interpretation, less a fact. " http://www.alphaitjournal.com/2008/07/spillner-big-projects-small-increments.html I like this quote under the heading “Antipatterns”:

“Partial delivery: not delivering into production. Unless delivering into production, “done” is more an interpretation, less a fact. ”

http://www.alphaitjournal.com/2008/07/spillner-big-projects-small-increments.html

]]> By: Andrew http://www.nettpar.org.uk/2010/02/14/done-is-really-done/comment-page-1/#comment-284 Andrew Wed, 17 Feb 2010 10:37:57 +0000 http://www.nettpar.org.uk/?p=343#comment-284 Yes. The switching of features makes more sense on a big codebase with a lot of developers. Yes. The switching of features makes more sense on a big codebase with a lot of developers.

]]> By: Phil Wilson http://www.nettpar.org.uk/2010/02/14/done-is-really-done/comment-page-1/#comment-282 Phil Wilson Tue, 16 Feb 2010 20:11:49 +0000 http://www.nettpar.org.uk/?p=343#comment-282 Of course, I mean "IMO" rather that "fwiw" :) Of course, I mean “IMO” rather that “fwiw” :)

]]> By: Phil Wilson http://www.nettpar.org.uk/2010/02/14/done-is-really-done/comment-page-1/#comment-281 Phil Wilson Tue, 16 Feb 2010 20:11:22 +0000 http://www.nettpar.org.uk/?p=343#comment-281 fwiw the whole "ifdef" method of switching on features doesn't seem like a good fit unless, like flickr, you're spending a lot of time working on a single largeish product with many interacting parts. For the kind of work we do (small projects, short sprints) optmising the deployment and rollback procedure, and deploying to a cluster would seem to solve a lot of problems without introducing additional overheads to the codebase. fwiw the whole “ifdef” method of switching on features doesn’t seem like a good fit unless, like flickr, you’re spending a lot of time working on a single largeish product with many interacting parts.

For the kind of work we do (small projects, short sprints) optmising the deployment and rollback procedure, and deploying to a cluster would seem to solve a lot of problems without introducing additional overheads to the codebase.

]]>