http://www.codingthearchitecture.com/tags/build-or-buy/ Software architecture for hands-on software architects en Coding the Architecture Fri, 26 Sep 2008 13:09:00 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://www.codingthearchitecture.com/2007/11/12/do_you_need_to_build_it_yourself.html <p> I've worked in many organisations and one thing that never ceases to amaze me is how often teams build unnecessary tools and frameworks. </p> <p> Yet again, I have to use a bespoke defect tracking system. This is the third one I've come across and none of them are as good as a Commercial off the Shelf (COTS) solution and definitely cost more to develop than to buy. </p> <p> In the past, I've also seen in-house developed: IDEs, email clients, database admin tools, UML tools etc. Perhaps it's more fun to write tools than the boring, business functionality your client/users needs but does it offer any value? </p> <p> As a software/systems architect it's your job to deliver value to the business you work for. Whenever someone suggests creating a bespoke tool ask yourself the following: </p> <ul> <li>Can I buy something to do this?</li> <li>Can I use or tailor an open source product?</li> <li>Can I use or create a template for a standard tool like Eclipse, Word or Excel?</li> </ul> <p> Be pragmatic in your decision and avoid wasting your limited time and resources on things you don't need to do! </p> http://www.codingthearchitecture.com/2007/11/12/do_you_need_to_build_it_yourself.html#comments http://www.codingthearchitecture.com/2007/11/12/do_you_need_to_build_it_yourself.html Mon, 12 Nov 2007 15:23:40 GMT