A lot of people talk about reusable code. The Pragmaic Programmer’s push the DRY (Don’t Repeat Yourself) Principal, which I’m a huge fan of. Hence this article. What you don’t see a lot is how writing reusable code pays off. Kyle and I have two (soon to be three) e-commerce sites (YumDrop, Fright Catalog, Import Costumes) up and running. YumDrop was built upon the code base origionally written by Kyle, Joe and Dan for Fright Catalog. We pulled out all the common parts and created a base that we could reuse. Then, Kyle took his CSS and created a basic framework he could reuse. What this meant for us as a development team was that we could roll new e-commerce sites in little time. For instance, Fright Catalog took Kyle, Dan, and Joe about 6-8 months to roll out. YumDrop took us probably 2 months after we finished componentizing the codebase. Import Costumes will take us about a month to roll out. Now that’s what I call seeing the real world impact of writing reusable code.