Navneet Panchariya - Web Designer | UI Designer | Front End Developer

The internet was abuzz for a long time, and the debate continues. To code or not to code? It remains a charged topic with strongly opinionated advocates on both sides. Let's put it to rest. It's 2015. Web design has come a long way. We have ridiculously specialized roles now (like "User Experience Analyst"); it's no longer one designer plowing through the full development stack on their own. We have better tools and efficient best practices. Let's examine both sides of the argument: Why you don't need to code With the right tool, a designer simply doesn't need to know how to code to build a beautiful, functional, and responsive website. What's more, most designers simply don't want to code. And there's nothing wrong with that. It's called specialization. In the past, there was nothing designers could do to get around the necessary development work (if not by them, then by someone else). It was a necessary nuisance....

It's almost incomprehensible to build a website that isn't responsive. The technique has developed to the point that most designers no longer say, 'responsive web design,' we say, 'web design,' and mean exactly the same thing. Naturally, opinions differ on how to implement responsive techniques; many sites that claim to be responsive aren't; most sites that intend to be responsive are only superficially so; there are even a few fixed-width devotees clinging on in the face of all reason. But broadly speaking a responsive approach is the default option for all websites. To understand where responsive design is going, we need only to look at where it came from... Necessity is the mother of invention The rise of responsive web design goes hand in glove with the expansion of the mobile web. Even if developing an m. site, the exponential growth of mobile devices and the accompanying variety of screen sizes makes responsive design the clear ch...