[mnicole]

I'd agree with underdesign. I've long-emphasized the point that if you're working in interaction design or web development as a designer, you need to know these mediums in-and-out in order to not only be effective, but at this point in the game, hirable. When someone says they're a web designer, but they don't write any code or understand the gamut of possibilities, their designs are going to be lackluster, the workload handed off to the devs will be greater, and the end-result will likely be discernibly less stellar than if you were doing it yourself. Not to mention it's fun and far faster to iterate on if you get your workflow right (LiveReload, CSS pre-processor, etc).

There will always be a place for static designers in print, but the resources available to developers to make their sites look "good enough" for them (see the Bootstrap Effect or all of these free asset sites) means you're going to need to get your hands dirty to stay relevant to companies and freelance devs alike if you prefer to design for digital mediums.

[Inkdryer]

Well said. I'd like to even take it a step further and see designers and developers really, truly collaborating at every point in the process as opposed to the traditional model of designing something and handing it off to a development team. Just as bad is the model of developing a product and then handing over to a design to "make it look pretty." I'd love to see the teams all up in each other's grills from the moment of hunch to the shipped product. Very few teams, if any, work that way now (at least in Ohio) but I'd be excited to see how each could really challenge the other directly.