Web designers that can't do markup
elliotjaystocks.com
elliotjaystocks.com
The designer should not be considering how the images will be cut up, what CSS features will be used, etc. They should have some general knowledge of what is and isn't possible, and what works and doesn't (interface/design wise) on the web, but then they should throw the .PSD files over the wall and let the coders get to work.
Thinking about the implementation while working on the design can only result in a dumbed-down design, not something that pushes the edge of what's possible. The best sites I've worked on came from designers who threw me a loop, but I managed to reproduce their design anyway.
That's utterly crazy on the face of it, so why is it ok for designers to waste the time of developers?
For literally hours on end it is several million permutations of "move it 2px to the left, no, right, no, up, no down, I mean right align, I mean center, I mean split it, I mean add that element, I mean do this, do that" and worst of all "What do you think of x" like I have any opinion on the aesthetics / presentation of any given site. I simply couldn't care less, aesthetics and design do not appeal to me in any way shape or form; that's why I'm a developer and not a designer.
Isn't this one of the primary reasons we even have frameworks that have a seperation of concerns between presentation and logic? So that the artsy but code illiterate types can mess around at the surface layer without messing up the code? Is it really so much to ask that the designer just mess around in the view layer till their heart's content? It's in version control, it's not like they're going to permanently break anything. Yet I find it a sisyphean task to convince these people that they need to know this stuff and not to bother me with it.
Meanwhile, I get no code written because a designer can't figure out the simple semantics of html/css, basic version control and mess with firebug for themselves.
So no, I don't think it's ok.
I'm not saying the designer needs to know nothing - they need to know a bit about screen sizes and other topics related to design. Obviously we disagree, but I don't want my designers thinking about the code.
Secondly, they hand you a PSD with a design, that's tedious but easy enough. You can farm it out to someone who just does HTML/CSS and as another comment on this thread notes, that's a very high competition low margin market. I don't have a real problem with that, but the initial designs are never the finished product, there are iterations all the time, and the way I've seen them iterate is "oh we need an edit / delete / create button for this particular widget here, it needs to be aligned over here, no we need to move it six million times to decide, I don't know, use your intuition" like I should have some kind of intuition about design issues.
They're designers, they handle appearance and aesthetics, I have no interest in it whatsoever, I don't want to iterate six million psd's into their html/css counterparts, and I sure as hell don't want to have to handhold the designer at the stage the implementation is already finished and they decide they want to modify pixel margins and such.
The time spent handholding the designer on my current project vs actually doing my job and writing code is 70/30 in favour of handholding the designer. This is flat out ridiculous and I refuse to believe it ought to be par for the course because they couldn't be bothered to learn something as utterly basic as css and html. I didn't even want to learn them myself because I didn't see it as a coding issue but just ended up learning it by osmosis because it's not complex at all.