Live data from Hacker News

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

intenseminimalism.com

51–60 of 104 posts

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

#51
This might work for web design. In my experience, it doesn't work well for UI design.

The first law of UI design is that you will fuck up most of the time. Most of your ideas are going to be bad bad bad. If you think that every mock comes out of your workstation smelling like roses, then you're either deluding yourself or you're just knocking out something incredibly derivative. To be a good UI designer you have to say no all the time, and to all of your ideas.

So here's the problem. Static image mocks only paint about 60% of the picture when you're talking about modern (especially touch-based) interfaces. Static mocks don't give you enough information to accurately cull your ideas. Sometimes you need to build the damn thing, so you can touch it and move it and realize well damn, that wasn't such a great idea after all (or oh, this part really needs to be changed or the final, magical yeah, that's not too bad).

All of the best and most innovative UI designers that I've met have been able to build interactive mocks of their designs. Now - don't ask how they did it. It's spaghetti code that will curl your hair, frequently written using some arcane technology that might not even be supported anymore. But it works just well enough that they can use it to iterate on their ideas.

Now, you can split this job into two people. One a "designer" and one an "interactive mock engineer". In theory, it could work, but in practice I've found that it becomes hard for the designer to detect the flaws in the design. I'm not sure why. But the final product doesn't change as much. It doesn't evolve as much. It's rarely as good as it should be.

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

#52
post #26

Earlier quoted context omitted.

They must understand that user can (and should be able to) change (just the) font size, if not their designs are often useless.

Useless might be a tad strong. How many sites can you really change the font size? Unless of course you mean through the browser.

Why would they implement a feature that's in every browser anyway? They should just design the site so that changing the font size through the browser works.

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

#54
At first i thought the title was referring to backend work, or perhaps just jQuery and i completely agreed-- i wouldn't expect a programmer to be great at design either.

But it turns out that this blogger doesn't expect designers to actually make their designs into something tangible. It seems positively ludicrous to me that any designer that is designing for the web would think that not knowing HTML/CSS, and therefore putting out an unfinished product is acceptable. It's almost insulting-- learning HTML and CSS takes a month at most, so why won't this designer learn it?

Building a design for a web page without actually writing the HTML+CSS for it is being a print designer and expecting the client to finish the job.

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

#55

I disagree. Just to be clear, we're talking web design here in HTML/CSS, not actual programming in JavaScript or Ruby. HTML/CSS creates designs, just like pencils create sketches and paint brushes create painting. Sure, it's hard, but watercolor and oil painting is also hard and has to be learned. Web design is no different. IMO, in a team, creating the HTML and CSS is a responsibility of the designer. The developers…

Probably you never met amazing designers that can't even put a "." at the end of their sentences. People are different, with different mind, and intelligences. Forcing such a designer to "code" is just going to destroy his skillset, that otherwise would be of great use in a good and collaborative team. :)

[deleted]

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

#56
The problem that I have with designers is not so much that they should code(I make iOS apps btw)....Its that they spend far too less time photoshopping (probably modifying a screenshot) and then after we work countless hours to make something like that...they would claim that they "designed" it and take a lot of credit for it..what they dont get is that the actual design of the application is not their photoshopped junk...it is in the design of the classes and how they interact with each other....all they did was style the app with pleasing colors and fonts and maybe some nice gradients...talk to them about how a consistent ui design is but a reflection of consistent object design and they will give you a blank stare (Oh no ...you started talking geek again!!)

They are not designers...they are stylers!!

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

#58
post #52

Earlier quoted context omitted.

Useless might be a tad strong. How many sites can you really change the font size? Unless of course you mean through the browser.

Why would they implement a feature that's in every browser anyway? They should just design the site so that changing the font size through the browser works.

Cause someone asks for it (or demands it)?

Buttons to change font sizes are anywhere in a browser's default chrome, therefore 99% of people don't know you can do it.

In general, I think it's dumb, but have been on the receiving end of "add font size buttons". No amount of "but you can just hit ctrl-+" does any good.

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

#59
The recent article he is responding to posits that designers who code are valuable. That is true. To debunk the claims properly he would need to show that designers who code are not valuable. Instead he debunked the straw man argument "designers should code".

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

#60
As a "web designer", HTML/CSS are your medium. If you don't understand your medium, you don't understand your craft. Last I checked, web browsers don't understand PSD files, which means without HTML/CSS the design isn't finished.

Imagine hiring a painter to do oil on canvas and they handed you a picture of a painting, or a sketch of what the finished painting should look like. You hired them for oil on canvas - not something that looks like oil on canvas.

When hiring a designer for a web project, I expect to receive html files that can be opened in a browser. In the very few cases where the designer didn't know HTML/CSS, I hired a designer who did to finish the job - because the inherent decisions with modeling a website in HTML/CSS are design-minded decisions.

As such, I suppose as a designer you don't HAVE to know HTML/CSS, but then I can't think of a single reason to hire you for a web project. Print, maybe - provided they understand the needs and limitations of printing and can provide files in a format the printer can use. Otherwise, I'm just going to have to hire a more talented designer to finish the job, which will leave me to wonder - why did I ever hire that first designer?

Post reply on HN