A few days ago I was talking with a friend of mine - and co-worker - about the future and news perspectives for front end development. So, at a certain point we started to talk about the real importance of the front end development if it could be compared to the cooking act.
So we started to wonder a bunch of things and "theorize" some others. In our concept, nowadays you can think on the cooker, and cabinets and taps as your infrastructure. The spoons and blenders and processors would be your tools, frameworks and helpers, the cookbook would be something like stackoverflow (ha-ha), snippets and, of course, the developer brain. So, the backend development would be in a position to check all the timings, if we are working with the correct infra, link and organize all those things, provide the checks like if the ingredients are good or not, if they're correct, wash, peel etc.
So, where's the Front End Developer? We were checking and selecting all the ingredients based on our clients choices, expectations and habits. We were driving, the cooking process in a way to order, organize and synthesise all the steps, because we know that are a million ways to cook rice, but only a few ways to cook an excellent rice. We have assembled the plate exactly how it was meant to be, and turning all those separated needs, expectations and process in an intuitive, interactive, easy understandable and graceful thing - in our case, a tasteful and beautiful meal without loose the core business here: satisfy the hunger.
The frontend developer was taking care of the details that will turn that rice and all the other things not a simple meal, but an experience. We where putting all the parts together in order to reach, facilitate and ordenize the needings, enviroment, expectations and reactions (of both side, cause of course you dont want a fresh and alive fish on your plate), and all those things must be made in a way that kill the hunger turns into an easy, nice and good experience for all, including the non-cookers.