Comments on: Don’t build a framework! http://notgartner.wordpress.com/2004/02/28/dont-build-a-framework/ Mitch Denny, Principal Consultant at Readify Sun, 12 Jul 2009 01:45:19 +0000 http://wordpress.com/ hourly 1 By: Mitch Denny http://notgartner.wordpress.com/2004/02/28/dont-build-a-framework/#comment-735 Mitch Denny Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2004/02/28/dont-build-a-framework/#comment-735 There is also an important distinction between identifying a pattern in your solution. Here you need to judge whether spending a very small amount of time abstracting out a very specific problem is worthwhile. <br /><br /> But I guess thats a harvested framework :) At the end of the day you need to see a pay-off for every piece of code that you write, considering more code = more bugs (in general). There is also an important distinction between identifying a pattern in your solution. Here you need to judge whether spending a very small amount of time abstracting out a very specific problem is worthwhile.

But I guess thats a harvested framework :) At the end of the day you need to see a pay-off for every piece of code that you write, considering more code = more bugs (in general).

]]> By: Blair http://notgartner.wordpress.com/2004/02/28/dont-build-a-framework/#comment-734 Blair Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2004/02/28/dont-build-a-framework/#comment-734 There has to be a little bit of irony in someone wanting to build a framework over a framework. Keep the posts coming. There has to be a little bit of irony in someone wanting to build a framework over a framework. Keep the posts coming.

]]> By: Scott McCulloch http://notgartner.wordpress.com/2004/02/28/dont-build-a-framework/#comment-736 Scott McCulloch Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2004/02/28/dont-build-a-framework/#comment-736 Hi Mitch - we have a foundation framework at CSC, because we do a ton of small projects which are very similar, after the many years of writing the applications (with very little componenet re-use), we took a look at the generic services we were providing in each, and built a core that we would take to each project - we have based a lot of those core services on providers.. fortunately a lot are in whidbey - but since its delayed then i guess we will keep ours for a while longer. <br /><br /> Our framework also contains a lot of tools, codesmith templates, and a lot of helper classes for handlings things such as nulls, objects, skinning, database interactions. Of course a lot of these are either application blocks, sections of open source applications, or custom written. <br /><br /> We just wanted a base to start from, to help provide consistency for our support environments mainly. We have found that the framework has provided some level of standardisation in the solutions we deliver - which can't be a bad thing? We took about 4-6 weeks to write the framework with primarily 1-2 people. Hi Mitch – we have a foundation framework at CSC, because we do a ton of small projects which are very similar, after the many years of writing the applications (with very little componenet re-use), we took a look at the generic services we were providing in each, and built a core that we would take to each project – we have based a lot of those core services on providers.. fortunately a lot are in whidbey – but since its delayed then i guess we will keep ours for a while longer.

Our framework also contains a lot of tools, codesmith templates, and a lot of helper classes for handlings things such as nulls, objects, skinning, database interactions. Of course a lot of these are either application blocks, sections of open source applications, or custom written.

We just wanted a base to start from, to help provide consistency for our support environments mainly. We have found that the framework has provided some level of standardisation in the solutions we deliver – which can’t be a bad thing? We took about 4-6 weeks to write the framework with primarily 1-2 people.

]]>