Jump to content
â€œ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.