What is the Future of Front End Web Development?

I think Chris nails it with this one on the head, but the whole article is really worth the read:

What websites are being asked to do is rising. Developers are being asked to build very complicated things very quickly and have them work very well and very fast.

The rate at which the complexity of our jobs is rising is astronomical. However, the final result — which still just a “website” to a layman/user — doesn't necessarily reflect that. People still think that when they are commissioning a website today, that it's the same type of work that it was five years ago, when in fact it is anything but.

To add to Chris' main question from the article, we often get asked “what it means being a front-end developer nowadays?”

While five years ago it meant knowing how to write semantic markup, and know your way around various browser quirks when it came to styling, today it's a completely different beast. There are states to be managed, something called “components”, and a whole lot of JavaScript (as Chris nicely listed it in the original article).

I'm here for the TL;DR, man. Can you just tell me should designers code? 

My answer is still the same, but I can now definitely add something to it. Yes, designers should code as in knowing how HTML, CSS, and JS work, and they need to be aware of how they affect performance in the browsers. They don't necessarily need to be able to build the interfaces they design themselves, as long as they are aware of the technologies being used.

This essentially means that designers should know how to code as if it were five years ago.

Next up

There doesn't need to be an app for that

We hear a lot of talk lately about the technical debt programmers are facing, once their software becomes mature enough, and all that rapid development that was done initially starts to hurt the company.

Read on →