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
/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
posted by WWWGeek at
1/24/2006 09:16:00 AM
