[codecraft] cleaning up code every seventh sprint

[Michael Bar-Sinai]

Thanks for the link. As for saving cycles for clean up - super important, often not understood enough by the management. And that's including me when I manage projects and have to push features through the door :-/

> On 21 Aug 2017, at 4:32, Philip Durbin <philipdurbin at gmail.com> wrote:
> 
> I've been reading "Coders at Work" by Peter Seibel and I found this exchange with Douglas Crockford interesting:
> 
> Seibel: In one of your talks you quoted Exodus 23:10 and 11: "And six years thou shalt sow thy land, and shalt gather in the fruits thereof: But the seventh year thou shalt let it rest and lie still" and suggested that every seventh sprint should be spent cleaning up code. What is the right time frame for that?
> 
> Crockford: Six cycles---whatever the cycle is between when you ship something. If you're on a monthly delivery cycle then I think every half year you should skip a cycle and just spend time cleaning the code up.
> 
> Seibel: So if you don't clean up every seventh cycle you may be faced with the choice of whether or not to do a big rewrite.
> 
> http://www.recursion.org/2013/1/6/insights-from-coders-at-work <http://www.recursion.org/2013/1/6/insights-from-coders-at-work>
> _______________________________________________
> codecraft mailing list
> codecraft at or8.net
> http://or8.net/mailman/listinfo/codecraft

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://or8.net/pipermail/codecraft/attachments/20170825/3e70b158/attachment.html>