The Great Buy Vs. Build Debate – Part IV
Ok, so enough of all of the talk about the nuances of this principle. I’ve added so much content to its explanation that if I were to append these last three posts to the original explanation, no one would ever read it. So as I wrap this series of posts up, I’m going to sign off with some guidance around these principles. Concrete statements that may help to avoid the three confusion points I covered when I introduced this series. So here they are, with links back to the original post.
Principle: Prefer Packaged Solutions
Guidance:
- Pursue a mixture of purchase, configuration and construction for a given tool or solution
- Rely on configuration where possible and building where unique and critical
- Buy/ reuse as much and many times as you can, then build the rest
Putting it another way, Leo De Sousa shares some principles of his own on this topic. He’s much more succinct than I am and they are right on the money.
Do these sum it up? If not, feel free to comment and provide some of your own thoughts.
@BrandonSatrom
- RT @elijahmanor: #HTML5 Boilerplate Version 3.0 is OUT! by @h5bp http://t.co/h8nTp2bK 2 hours ago
- Parallax effects with Stellar.js - http://t.co/b5EA0Ail 4 hours ago
- RT @scichelli: Oh, hey, and the first @PolyglotATX meeting is this Thursday! Join us. :) http://t.co/mdj9ENpz 5 hours ago
Tags
.net analogy architecture asp.net asp.net mvc BDD blog C# CoffeeScript communication composition conference conferences ddd design development EA events fun google HTML5 javascript job knockout language links meta microsoft mvc mvccontrib mvvm oss screencast series speaking tdd technology travel ux video WatiN web 2.0 wf workflow writingCategories







