Comments on: Keeping It Clean

By: jeremy

jeremy — Wed, 28 Apr 2010 21:25:06 +0000

Yes, our feeling is that the one day we spend every 6 weeks is well worth the investment. Conversely, if we didn’t spend the day that way, we feel we would end up paying a larger price later.

By: pedro

pedro — Wed, 28 Apr 2010 17:50:59 +0000

That is a great idea. Can you afford to spend one full day refactoring?

By: Yoav Shapira

Yoav Shapira — Mon, 15 Mar 2010 04:27:50 +0000

Good stuff. Thank you for sharing!

By: Auren Hoffman: To Grow a Company, You Need to Be Good at Killing Things | Blog All Over The World

Mon, 15 Mar 2010 04:17:38 +0000

[...] setbacks and long debugging hours after a lot more code has been written on top. Rapleaf holds "Sweepleaf" days semi-monthly where engineers do nothing but cleaned up and streamline code. People – [...]

By: Auren Hoffman: To Grow a Company, You Need to Be Good at Killing Things

Auren Hoffman: To Grow a Company, You Need to Be Good at Killing Things — Sun, 14 Mar 2010 22:56:10 +0000

[...] and long debugging hours after a lot more code has been written on top. Rapleaf holds “Sweepleaf” days semi-monthly where engineers do nothing but cleaned up and streamline [...]

By: Auren Hoffman: To Grow a Company, You Need to Be Good at Killing Things | Deconstructing The News

Sun, 14 Mar 2010 22:15:17 +0000

[...] and long debugging hours after a lot more code has been written on top. Rapleaf holds “Sweepleaf” days semi-monthly where engineers do nothing but cleaned up and streamline [...]

By: Manish Manchanda

Manish Manchanda — Tue, 09 Mar 2010 09:55:29 +0000

One issue though which i can see is that coders(coz lack of time) would write smelly / duplicated code and add a task to Sweepleaf tasks to get off the gilt.
How to make sure that Sweepleaf tasks are not used as alibi to write crappy code.