The line between developer and designer has been blurring for some time and will only continue to do so (hopefully! if our tools and abstractions keep becoming

The line between developer and designer has been blurring for some time and will only continue to do so (hopefully! if our tools and abstractions keep becoming better). Often I find myself on the other side of what you stated, where the designer leaves me (the developer) as the de-facto designer. And the main reason why is that the designer is only capable of thinking in their toolset, which happens to usually be photoshop. PS simply doesn't cut it dealing with the complexity of web applications in all the different form factors it needs to work on. This has lead me to believe that if you're a web designer, your medium is HTML/CSS and potentially JS. So you should understand and be fluent in it. The designer is responsible for actually building out the html templates/styling used, and the developer is responsible for bringing those to life, but each has a lot of input at every step. A lot of crossover builds better projects :)