Jump to menu

Vote down?

  1. Andy Clarke

    @Mathias Bynens,

    “Obviously, you’re talking about minor changes, not fundamental modifications to the original design — let alone, starting a new design from scratch.”

    — Of course, new creative concepts take more time, but even these never need me to change HTML. Changes to layout are simple and mean only working in CSS.

    “I can see why the only changes clients request to your designs are tiny ones, but this doesn’t mean this is the case for every designer and for every project.”

    — No, I often go back to the drawing board. I’ve been known to throw away designs even AFTER the client had signed them off, because I wasn’t happy with the direction.

    “This workflow might work for your projects, but this doesn’t mean it’ll work for any web design + development project. ”

    — Did I infer that it would?

    “Again — I think the situation in which there’s both a designer as well as a (front-end) developer is much more common than just one double- or triple-talented bastard doing all the work.”

    — I don’t do all the work. I have enormously talented chaps to work with, including Owen Gregory (the best partner I have ever worked with) . Oh, and web designers should learn markup and CSS. Otherwise they aren’t web designers.

    “There’s no way the front-end developer is gonna start working before the design is final (i.e. fully approved by the client). It’s called “working for free”.”

    — Where I live, it’s called “tripe” — and that argument is full of it and based on generations old preconceptions about what designing, prototyping and developing is.

    “This article is, sadly, a fairy tale to most people.”

    — Damn. I knew I had forgotten to mention something. I should have said that Mike loved the web site only after drinking a special potion (I slipped it into his tea). I also turned Sam into a frog (or was it a stone) when she brought up IE6.