Small Projects
Posted by Adam Wiggins on March 31, 2008 at 06:19 PM
Tiny projects keep it new, for sure. It seems to tie in a little bit with proof-driven development and personal projects - in each case, you're escaping the mental cage of a monolithic, mature product to start something new. (Even if the "something new" is a component that's going to plug in to said mature product.)
Recently I've been dividing up the the Heroku architecture more finely. We've gone from about three repositories to over a dozen. Each time we carve off a new piece, it's a chance to freshen things up. A new revision control system, a new framework, or even just a new class hierarchy. Breaking free of the past is liberating.
Comments
There is 1 comment on this post. Post yours →
The point is to keep things fresh and still work in the general area of your business. Not to waste time on foolish things, like I witness so many of my peers doing.
If your going to work on "Tiny projects", let them be based on, or around, the projects that are making you the $$$. I prefer to work on research projects for future applications.
Post a comment
Required fields in bold.