Comments on: 37 Questions Web Designers/Developers Should Know the Answer To

By: Agus Pelani

Agus Pelani — Tue, 13 Nov 2007 03:36:17 +0000

awesome articles……:D..very helpful for some designer like me..but should I learn these 37 step questions,mmmm…any designer cannot do that..isn’t it?

By: Michael Persson

Michael Persson — Thu, 09 Aug 2007 07:39:55 +0000

Graphic designers are mostly graphics, printing and artistic and creative experts while a web designer are coding experts and have fortunately expert experience in web graphics, loading time, usability and Search Engine Optimization, xhtml and css.. knowledge.

These are two different jobs and cant be competitive but co-operative supporting each other professionally.

By: Felipe LÃ³pez

Felipe LÃ³pez — Tue, 19 Jun 2007 19:43:38 +0000

Good Article i think that it could be better with the correct answers

By: Michael Persson

Michael Persson — Sat, 05 May 2007 12:01:37 +0000

I like this site, in inspires me to see other web developers and designers make a good job

Keep up the good work..

Michael Persson

By: Calle GrÃ¶nlund

Calle GrÃ¶nlund — Tue, 20 Mar 2007 10:25:39 +0000

As the others mentioned I also think this far more Developer biased. Web design can be a broad area, but you still need to be a designer. I’ve seen too many crash and burns from developers who think 100% reasoning equals a good design. Sometimes it works, but you really really have to be and exceptional developer to achieve that.

I’m more of an all-around designer in every area of design (with this I mean industrial, graphical, web, furniture, game etc.) and I’ve had a good share of battles with the nemesis of designer vs. developer/engineer.

I mainly think it’s a symbiosis between the two. Designers are here to bend the rules and create something unique. Developers/engineers are there to make it possible and to keep it in balance. It HELPS for both sides to know about the others profession, but should they know it as a reflex? No. It starts to interfere with the process and in worst case scenarious it will cripple it.

I’ve learned that in a design process (can pretty much be anything from spoons to marketing) it’s a good beginning to use a 50/50 balance between the two, but when the product is getting closer to the final state the balance should be 60-70/30-40 (can be turned any way around you want). 50/50 is compromise between everything and finally leads to mediocre result.

As for this list, there are very few things are related to design (and most of them are really stretched).

By: JuliÃ¡n Rodriguez Orihuela

JuliÃ¡n Rodriguez Orihuela — Tue, 20 Mar 2007 06:55:20 +0000

Well, they had me at “BOM”… and I still don’t fully understand what it is…

By: ia

ia — Tue, 13 Mar 2007 22:27:34 +0000

Regarding Michael’s comment, I think you’re limiting the duty of a designer when the entry mentioned web designer. Web designers manipulate HTML. It is not a question of developing versus designing. Developers can be web designers, and so can “typical” designers like graphic designers and other aesthetically inclined people. In fact, anybody who comes in contact should read the answers to these questions to understand the Why behind the What.

As for the article, that was a good spin on the Sitepoint article. Crafty. :)

By: Michael Cober

Michael Cober — Sat, 10 Mar 2007 21:46:07 +0000

Hmmm,

Good questions…. for a developer.

I think a designer would be better equipped with questions about colour theory, effective use of the elements and principles of design (line, shape, direction, size, texture, colour, value, balance, gradation, repetition, repetition, contrast, harmony, dominance, & unity, and of course a strong typographic understanding. The answers to these questions would just seal the deal.

Like I said, a good list for developers, but for a designer the aesthetics should be more important than the appropriate DOCTYPE.

Cheers