4 ms·

>I wouldn't expect a plasterer to fit my windows on my house. I don't think that analogy fits. A more apt analogy would be "an architect creates the construct

by bluthru 13y ago

>I wouldn't expect a plasterer to fit my windows on my house. I don't think that analogy fits. A more apt analogy would be "an architect creates the construction documents for his/her designs." I'm an architect and I can also do web design and front-end development (with some light server-side code). Understanding the medium is essential to be a good designer. Html/css informs visual design for the web, just like materiality and structure informs building design. Design thrives on informed constraints--otherwise it's just art. Some web designers today go straight to code after some sketches.

EnderMB 13y ago
The analogy is the least important part of the post. The argument still stands that a designer designs and a developer develops. Some designers do go straight to code, but usually in a prototyping stage and absolutely not as a build for a final website. The original post is about outlining a job title, and anyone that has worked with a half-decent designer will know that there is FAR more to design than simply setting up a PSD or sketching out a structure, using either a prototyping tool or straight in code (using something like Zurb Foundation). I'd argue that there's far more to understanding the medium, and the constraints of building for the web. Any design agency will run a business through a number of processes to come up with a design that accurately represents them, before ANY design work has been done. UX is a part of this, but there are also many other stages in planning. Some agencies are big on archtypes, some are big on kick-off workshops. When you take all that stuff into consideration, the analogy isn't so far off. What a lot of professional designers do is very far from mocking up a structure in code or in a PSD. On the flip side, I know some designers that do create prototypes using something like Foundation, but very few of them would ever want to be trusted with a front-end build for a real project.

by bluthru 13y ago

EnderMB 13y ago

The analogy is the least important part of the post. The argument still stands that a designer designs and a developer develops. Some designers do go straight to code, but usually in a prototyping stage and absolutely not as a build for a final website. The original post is about outlining a job title, and anyone that has worked with a half-decent designer will know that there is FAR more to design than simply setting up a PSD or sketching out a structure, using either a prototyping tool or straight in code (using something like Zurb Foundation). I'd argue that there's far more to understanding the medium, and the constraints of building for the web. Any design agency will run a business through a number of processes to come up with a design that accurately represents them, before ANY design work has been done. UX is a part of this, but there are also many other stages in planning. Some agencies are big on archtypes, some are big on kick-off workshops. When you take all that stuff into consideration, the analogy isn't so far off. What a lot of professional designers do is very far from mocking up a structure in code or in a PSD. On the flip side, I know some designers that do create prototypes using something like Foundation, but very few of them would ever want to be trusted with a front-end build for a real project.