http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/ For engineers, by engineers. Thu, 09 Feb 2012 03:22:26 +0000 hourly 1 http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-7783 How to Survive Wiping Your Database Wed, 07 Sep 2011 20:25:09 +0000 http://blog.rapleaf.com/dev/?p=390#comment-7783 [...] Managing multiple schemas has been a bit of a pain point for us in the past, and during our latest Sweepleaf we set out to create a tool that would help us run multiple sets of migrations from within a single [...] [...] Managing multiple schemas has been a bit of a pain point for us in the past, and during our latest Sweepleaf we set out to create a tool that would help us run multiple sets of migrations from within a single [...]

]]> http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-2752 jeremy Wed, 28 Apr 2010 21:25:06 +0000 http://blog.rapleaf.com/dev/?p=390#comment-2752 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. 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.

]]> http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-2742 pedro Wed, 28 Apr 2010 17:50:59 +0000 http://blog.rapleaf.com/dev/?p=390#comment-2742 That is a great idea. Can you afford to spend one full day refactoring? That is a great idea. Can you afford to spend one full day refactoring?

]]> http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-2732 Yoav Shapira Mon, 15 Mar 2010 04:27:50 +0000 http://blog.rapleaf.com/dev/?p=390#comment-2732 Good stuff. Thank you for sharing! Good stuff. Thank you for sharing!

]]> http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-2722 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 http://blog.rapleaf.com/dev/?p=390#comment-2722 [...] 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 - [...] [...] 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 – [...]

]]> http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-2712 Auren Hoffman: To Grow a Company, You Need to Be Good at Killing Things Sun, 14 Mar 2010 22:56:10 +0000 http://blog.rapleaf.com/dev/?p=390#comment-2712 [...] 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 [...] [...] 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 [...]

]]> http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-2702 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 http://blog.rapleaf.com/dev/?p=390#comment-2702 [...] 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 [...] [...] 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 [...]

]]> http://blog.rapleaf.com/dev/2010/01/19/keeping-it-clean/#comment-2692 Manish Manchanda Tue, 09 Mar 2010 09:55:29 +0000 http://blog.rapleaf.com/dev/?p=390#comment-2692 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. 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.

]]>