<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d13376580\x26blogName\x3dThe+GeekWithin\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://geekwithin.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://geekwithin.blogspot.com/\x26vt\x3d3997356767057402239', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

The GeekWithin

Tuesday, January 24, 2006

To Framework or Not To Framework

An article on Reg Developer titled "The 'f' in framework" has given me food for thought.

/begin rant

Do we really need to design complex frameworks, or even buy complex management systems for our websites? Almost every project I have been on the first thing that is suggested is the purchase of a framework or some workflow system. To me these add a complexity that needs to be addressed, they do NOT automaticaly fix your problems.

I also find it annoying that just because someone says they want workflow that it means we need a system to manage it. Hello?!? Maybe they just want you to pay attention to how they use the app and how it needs to guide them through the business process.

/end rant


 

Creative Commons License  This work is licensed under a Creative Commons Attribution-ShareAlike 2.5 License.