Comments on: problem solving - designer and the developer http://www.rega.in/2008/11/18/problem-solving-designer-and-the-developer/ Mon, 06 Sep 2010 23:43:20 +0000 http://wordpress.org/?v=2.6.1 By: kaa http://www.rega.in/2008/11/18/problem-solving-designer-and-the-developer/#comment-358 kaa Tue, 18 Nov 2008 11:14:45 +0000 http://rega.in/?p=335#comment-358 @rasheena - agreed. you may argue between a pipeline production and agile methodology. and sure in some scenarios one would be better and in others the other would be. What I am saying here is at the very least there should be some method. That people should realize that designers do more than just prettying up there work. the design is more than just UI (if we consider software)...or looks would be a general word. And I am talking this with experience i have gained working with small teams, startups. this would also be true with open source software. @rasheena - agreed. you may argue between a pipeline production and agile methodology. and sure in some scenarios one would be better and in others the other would be.

What I am saying here is at the very least there should be some method. That people should realize that designers do more than just prettying up there work. the design is more than just UI (if we consider software)…or looks would be a general word. And I am talking this with experience i have gained working with small teams, startups. this would also be true with open source software.

]]> By: Rashina http://www.rega.in/2008/11/18/problem-solving-designer-and-the-developer/#comment-357 Rashina Tue, 18 Nov 2008 09:39:28 +0000 http://rega.in/?p=335#comment-357 This seems to be the traditional procedural approach to development (like pipeline production) where the product goes from one hand to another and is worked upon sequentially. With the latest methods of working (for instance Agile methodologies), one can imagine the problem been solved to a great extent by a simple gathering of designers, developers, testers, customers at once...to work on and discuss the final product from conception to delivery. So while designers can convey the design and usability issues, the developer can discuss the implementation or technical limitations, and customer can say if they like the sound of it. This seems to be the traditional procedural approach to development (like pipeline production) where the product goes from one hand to another and is worked upon sequentially.

With the latest methods of working (for instance Agile methodologies), one can imagine the problem been solved to a great extent by a simple gathering of designers, developers, testers, customers at once…to work on and discuss the final product from conception to delivery. So while designers can convey the design and usability issues, the developer can discuss the implementation or technical limitations, and customer can say if they like the sound of it.

]]>