3 ms·

> Writing markup absolutely is part of design So you'd expect a designer to be able to write concise mark-up that works on all required browsers, works well on

by EnderMB 13y ago

> Writing markup absolutely is part of design So you'd expect a designer to be able to write concise mark-up that works on all required browsers, works well on modern mobile devices and writes clean code? If so, I'd like to meet someone that fits this description. For the gist of my argument, please read through my other comments on this. Your argument about workplace is very loaded towards your argument. Agencies are very specialised work places, but you talk about it as if it's a negative thing. Surely, it is essential for such companies to specialise because agencies are expected to work across a wide range of clients, and to have the experience to handle the full digital process? I've worked in a startup before, a non-technical startup, and even they had the sense to hire a good designer to handle a redesign. I'm "insistent" that a designer should design because that's their job title. I've never stated that a designer should never touch HTML, only that a designer shouldn't be expected to write HTML to the same level of quality as a front-end developer. > The site you are writing this on was created by the author of Hackers and Painters after all :) And how many designers would be happy to put this design on their portfolio?

grey-area 13y ago
So you'd expect a designer to be able to write concise mark-up that works on all required browsers, works well on modern mobile devices and writes clean code? If so, I'd like to meet someone that fits this description. Yes I would - it's not rocket science, though I'm not really interested in satisfying your demands for internet proof, sorry. If I were hiring a web designer I'd prefer one who was familiar with HTML and used it to design up to final templates over one who didn't, though of course I'm sure there'd be exceptions - there's no need for dogmatism about what makes a good designer. Specialisation also has drawbacks, and it's quite possible to be a bad specialist, just as it's possible to be a mediocre generalist. That doesn't mean that all generalists are incapable of producing clean HTML or good code, or that good designer means that they don't do development, and they stick to photoshop.
- EnderMB 13y ago
  > Yes I would - it's not rocket science, though I'm not really interested in satisfying your demands for internet proof, sorry. If I were hiring a web designer I'd prefer one who was familiar with HTML and used it to design up to final templates over one who didn't, though of course I'm sure there'd be exceptions - there's no need for dogmatism about what makes a good designer. There's a huge difference between being "familiar with HTML" and what I described. It's this difference that can make or break a number of projects, especially when you're working on big budget jobs for clients that require legacy browser compatibility. > Specialisation also has drawbacks, and it's quite possible to be a bad specialist, just as it's possible to be a mediocre generalist. That doesn't mean that all generalists are incapable of producing clean HTML or good code, or that good designer means that they don't do development, and they stick to photoshop. It's possible, but they're often the exceptions that prove the rule. Either way, it's a huge stretch to call a developer specialising because they do "development".

by EnderMB 13y ago

grey-area 13y ago

So you'd expect a designer to be able to write concise mark-up that works on all required browsers, works well on modern mobile devices and writes clean code? If so, I'd like to meet someone that fits this description. Yes I would - it's not rocket science, though I'm not really interested in satisfying your demands for internet proof, sorry. If I were hiring a web designer I'd prefer one who was familiar with HTML and used it to design up to final templates over one who didn't, though of course I'm sure there'd be exceptions - there's no need for dogmatism about what makes a good designer. Specialisation also has drawbacks, and it's quite possible to be a bad specialist, just as it's possible to be a mediocre generalist. That doesn't mean that all generalists are incapable of producing clean HTML or good code, or that good designer means that they don't do development, and they stick to photoshop.

EnderMB 13y ago
> Yes I would - it's not rocket science, though I'm not really interested in satisfying your demands for internet proof, sorry. If I were hiring a web designer I'd prefer one who was familiar with HTML and used it to design up to final templates over one who didn't, though of course I'm sure there'd be exceptions - there's no need for dogmatism about what makes a good designer. There's a huge difference between being "familiar with HTML" and what I described. It's this difference that can make or break a number of projects, especially when you're working on big budget jobs for clients that require legacy browser compatibility. > Specialisation also has drawbacks, and it's quite possible to be a bad specialist, just as it's possible to be a mediocre generalist. That doesn't mean that all generalists are incapable of producing clean HTML or good code, or that good designer means that they don't do development, and they stick to photoshop. It's possible, but they're often the exceptions that prove the rule. Either way, it's a huge stretch to call a developer specialising because they do "development".