Programmer who knows good design
- Started
- Last post
- 55 Responses
- gramme0
I hear you rounce, but that's why I included the caveat about knowing the strengths and limitations of technology. It's just like with printing. There are things you can and can't do with different printing presses, papers, inks, and formats, just as in web design. One doesn't need to know how to do color separations, create plates, or mix Pantone inks in order to design appropriately for the printed medium. Same with web.
- gramme0
Also, I would beg to differ about it "showing in the final product" when the designer and developer are one. All you need are two smart, talented people with mutual respect and clear communication.
- ukit0
One doesn't need to know...but you'll gain a lot by knowing it.
- BattleAxe0
actually collaboration in my experience has generated the best results.
Designer does layout in whatever graphics program
Developer 1 makes it a functional working webpage
Developer 2 then integrates the back end, database functionality
sadly where I currently work everyone likes to wear all kinds of hats to impress big wigs and the Developers end up doing there own UI's and well barf
- gramme0
Right ukit, a designer doesn't need to know the language, merely what it can do. With that knowledge—and staying ahead of the curve on what various languages can do and how they're evolving—a designer will be well-equipped to design beautiful websites without having to write a single <br>.
- Milan0
Designers who have never built out a page in HTML/CSS got no business designing websites, and should stick to print.
- pffffffttt
Meeklo - This is bullshit Milan.gramme
- (or, what Meeklo said)gramme
- interactive design and print design are 2 different thingsMilan
- of course they are, but what you said right there makes no sense, and being a designer who does both, I almost find it insultingMeeklo
- offensiveMeeklo
- Well tough shit Meeklo, he has a point. =Prounce
- pffffffttt
- Meeklo0
^
if it wasn't for print designers, that know layout, grids, type and kerning it would be even harder to find well designed websites.
- doesnotexist0
it's a fairly normal thing to have to do- two different worlds.
take a vacation!
- Meeklo0
The real truth is that if a good programmer that knows how to design shows at your desk, you will be out of a job. (and he will get paid 3 times as much on your position too).
- ukit0
I think it depends more what your area of focus is...the people whose work I find most interesting are those who integrate visual design with interactivity and computation, like Mr Doob, Roxik or Yugo Nakamura (or John Maeda). Hard to imagine they would be able to create the same level of work by outsourcing the programming to someone else.
Obviously all exceptions to the rule but I think for most of us working in "interactive design" the principle isn't all that different.
- adev0
I must be weird. I enjoy taking my PSDs and creating the HTML/CSS from them down to the pixel. It's almost calming to do. When I would do this for an boss he'd be like "just make a box and put it here" or he'd just use the Insert Div command in Dreamweaver, not caring about the height/width exactly. I should start doing this as a service more.
- janne760
i know at least one programmer with a rare and great sensibility for design.
- SteveJobs0
i haven't read every response here, but when you work for bigger companies there's yet greater distinction to be made between the roles of a "Programmer" and a "Designer" as there's generally a third role which often facilitates the whole development process. This 3rd cog is often known as the "Front-End Developer". This is probably the thankless code-monkey the original poster was referring to.
Depending on the technology used, a true programmer generally won't even touch the front-end. The front-end being html, css, javascript, and in the case of technologies like .Net will likely not even be responsible for the server-side controls or the event handlers for those controls. They, will be working on building the implementation to the interfaces the "Architechts" build out or creating stored procs, or building API's for the front-end developer to use. They will build web handlers/web services, content-delivery network systems, caching systems, dll's and other low-level pieces - none of which are remotely related to the tasks the original poster referred to.
Having said all that, the front-end developer "should" have a solid understanding of cross-browser dev as it relates to CSS, HTML, Javascript and Ajax. They won't have the true sensabilities of a designer, just the competance and hopefully passion for that thankless line of work to code a pixel-perfect representation of what the designer gave them.
- ptouch7180
The role of a Good front end developer is far from that of a thankless code monkey. I feel that the design of anything interactive is more than what it looks like, its how it behaves. The front end developer is critical in facilitating interaction between user and interface, and turning a useless psd file into something real. Yes, a front end developer should have the visual acuity of a designer, but what some designers fail to realize is that this medium(interactive design) is plastic. Once an inDesign file has gone through a rip, plates burned, and is printed its done, forever. Once a PSD file has been authored in html and css, the design has only just begun. Browsers are all different, standards change, buttons do things. Anyways, my two cents.
Yo, Greggles, about to hop in the shower and head over!!!
p.s. What the hell is an interactive designer? someone one who interacts with their design application. lol