The “designers should code” bullshit and a not so new idea • Hacker News Board

Re: The “designers should code” bullshit and a not so new idea

#101

Post by tel » Sun, Sep 04, 2011, 2:39 PM UTC

folletto wrote: post #89

tel wrote: post #63

This article is plain non sequitur. The argument stated is that intelligence is multidimensional (stated as fact with caricature testimony) and therefore there exists a job aligned with one of those dimensions. Arguing that designers should code states that today optimal design is done by someone who has skill on multiple axes. So the article really just dodges the issue by defining situations alternative to argument…

That point is underlying the whole article. ;) What it tries to clarify - and well, it might have failed, of course - is that we should stop to simplify the problem as "designers should code", because not all designers should . But yes, all designers could , and if you feel that way, or you are prepared for that, or if you want that, you can learn to code. Exactly like a developer can learn how to design. In either c…

I think the difference is that the author defines "designer" as someone who excels in some "designer-like" quadrant of the intelligences. Which is a load of self-entitled bs.

A designer is someone who designs—it's defined by action, not beliefs about competency. If you design things implemented in HTML/CSS and you don't have any proficiency at all in those technologies then you're very liable to be a worse designer than someone who does. The argument of how often that is true is what's important here and it's never actually discussed in the article.

Re: The “designers should code” bullshit and a not so new idea

#102

Post by talmand » Tue, Sep 13, 2011, 2:32 PM UTC

schrijver wrote: post #85

talmand wrote: post #82

Earlier quoted context omitted.

Depends on how you look at it. Writing HTML is more like using Word in a formatting mode where you can see the code that's normally behind the scenes. The method you are referring to is similar to using a WYSIWYG editor. Plus it depends on how you define what "code" means.

Coming at this as a designer who learned to code in both senses of the word, I have to disagree with the sentiment that HTML/CSS is easy. Sure, the principle is rather straightforward, but writing CSS is tedious and error-prone and the HTML/CSS is combination is modeled on single column text based layouts… it’s shocking to find out there’s no built in support for columns and no way to vertically align an element, for…

As a designer who develops as well, I agree wholeheartedly.

Although I would say that HTML and basic CSS is easy. Getting creative with complex layouts using CSS can get challenging.

Re: The “designers should code” bullshit and a not so new idea

#103

Post by folletto » Wed, Sep 14, 2011, 2:08 PM UTC

knieveltech wrote: post #95

folletto wrote: post #87

Earlier quoted context omitted.

I worked with lots of excellent designers that aren't able to write a single line of code. And still paired in a good team with a developer, they did marvels. :)

So what you're saying is it's cool for someone to only learn half their job if you've got other warm bodies available to cover for them. Eh. Taken to an extreme this is similar to you saying I'd make an excellent plumber if I could drive the truck and had a couple of helpers that actually knew how to do plumbing. You can't tell me with a straight face that a designer that doesn't have a solid grasp of the underlying…

That's a nice metaphor, but no, we aren't saying that you are doing a job, and actually you don't know how do to it and you have someone else doing that for you. The plumber metaphor is flawed.

I can tell you, because it happen every day. It happens to me every day. And if you don't believe me, just read around the comments from people, here and on the article page, that do exactly that.

By the way, there are also comments of people saying that designer must think a bit over what's technically possible, to innovate. Figures. ;)

The problem however isn't in agreeing or not, but in not being so sure that your point of view is the right one.

And I'm talking with a straight face, yes. :)

Re: The “designers should code” bullshit and a not so new idea

#104

Post by folletto » Wed, Sep 14, 2011, 2:16 PM UTC

tel wrote: post #101

folletto wrote: post #89

Earlier quoted context omitted.

That point is underlying the whole article. ;) What it tries to clarify - and well, it might have failed, of course - is that we should stop to simplify the problem as "designers should code", because not all designers should . But yes, all designers could , and if you feel that way, or you are prepared for that, or if you want that, you can learn to code. Exactly like a developer can learn how to design. In either c…

I think the difference is that the author defines "designer" as someone who excels in some "designer-like" quadrant of the intelligences. Which is a load of self-entitled bs. A designer is someone who designs—it's defined by action, not beliefs about competency. If you design things implemented in HTML/CSS and you don't have any proficiency at all in those technologies then you're very liable to be a worse designer t…

However, you can design things implemented in HTML/CSS without actually knowing anything about HTML/CSS. ;)