Design Agnostic Development
Let's face it, the number of people out there in the world that can "design" a website are many. And there are just as many, if not more, that can develop for the web as well. So why is Design Agnostic Development so hard?
Design Agnostic Development is a term meant to say that developed code and output is done in a compliant manner and with minimal structure. This allows the developed piece of code to be inserted into any existing design with minimal effort. Why is that so important? Because ultimately things will change, people will change their view of your application and you will want to change how it looks and feels, but may not want to change the way it works. If you can do it with DAD then you would be able to change either the way it behaves or the way it looks WITHOUT affecting the other.
Design Agnostic Development is a method that is similar to "object oriented programming", only we're creating pieces of an app that don't have structure to them. We're designing an app that doesn't have a personality to it, just a simple output that can be customized and included accordingly.
If people would take more time to make sure their efforts are Design Agnostic, then they would actually spend LESS time developing and there wouldn't be as many issues between the designers and the developers on how thing interact. Make it DAD and you make it easy. Ultimately, that's what it's all about. Keep It Simple!
Design Agnostic Development is a term meant to say that developed code and output is done in a compliant manner and with minimal structure. This allows the developed piece of code to be inserted into any existing design with minimal effort. Why is that so important? Because ultimately things will change, people will change their view of your application and you will want to change how it looks and feels, but may not want to change the way it works. If you can do it with DAD then you would be able to change either the way it behaves or the way it looks WITHOUT affecting the other.
Design Agnostic Development is a method that is similar to "object oriented programming", only we're creating pieces of an app that don't have structure to them. We're designing an app that doesn't have a personality to it, just a simple output that can be customized and included accordingly.
If people would take more time to make sure their efforts are Design Agnostic, then they would actually spend LESS time developing and there wouldn't be as many issues between the designers and the developers on how thing interact. Make it DAD and you make it easy. Ultimately, that's what it's all about. Keep It Simple!
Post made: Wed, Feb 13 2008 - 14:38 PM
Category: General Webby Stuff
Tags: Design |Web Stuff |Development |
