News for hackers. Stuff that matters.
Re:What to Do When You’re the Only Designer They’ve Got by seanmcdirmid on Tuesday August 27, 2013 @07:49PM (#6287109)
Two points.

First, this is a very bad situation for a junior designer since they basically get no mentorship. The studio model is very important for developing design talent. Don't take on junior talent without senior talent if possible.

Second, expecting designers to code, a common meme repeated often on hackernews, is even more disastrous in this case; they are overloaded already with design work (and even if you have a few designers already, they will still probably be your bottleneck).

Re:What to Do When You’re the Only Designer They’ve Got by ryanSrich on Tuesday August 27, 2013 @08:49PM (#6287334)
As a designer who codes I've never understood this mentality. I sketch out wireframes, take them to PhotoShop, and flush out the HTML, CSS, and JS. Perhaps if the structure of your team isn't suited for this workflow it could end up hindering the design process but I find it to be quite enjoyable.
Re:What to Do When You’re the Only Designer They’ve Got by seanmcdirmid on Tuesday August 27, 2013 @10:56PM (#6287779)
So you do design and production (is HTML/CSS and a bit of JS really coding?), great! I have a feeling most web designers are in that boat, though I've never worked in that field before. Not all designers are web designers though.
Re:What to Do When You’re the Only Designer They’ve Got by fmilne on Wednesday August 28, 2013 @01:20AM (#6288165)
there is definitely a difference between knowing how to make a prototype and being able to code at a production level. Again, without mentorship it's difficult to learn the difference.
Re:What to Do When You’re the Only Designer They’ve Got by seanmcdirmid on Wednesday August 28, 2013 @05:01AM (#6288726)
Most developers are clueless as well. I can imagine a junior designer getting into a lot of trouble in a small dev shop given all the misunderstandings.