In the last two year I’ve contributed to the development of Sellf as a full-stack engineer. I worked mainly on the server side (in Ruby on Rails) at the beginning or our adventure, spending more and more time on the client part (in Ember.js) when we focused on the release of our webapp.
In the last months a lot of attention as been brought to the role of an engineer as a full-stack developer (FSD). Techcrunch talked about the rise and fall of the full stack developer, stating that nowadays an FSD needs to be a cross platform dev instead of an end-to-end one. This position has been criticized by some people, whom I agree with, who share the idea that an FSD is a person with a broad range of skills that cover the entire stack needed to release a fully featured app.
A good definition of FSD comes from George Fekete who says that FSDs are comfortable working with both back-end and front-end technologies. This is ok if the comfort-zone not only includes coding but also managing the infrastructure that hosts and runs the app code. Instead, I don’t put in the basket of the FSD skills all the things that concerns UI/UX design, because even if it is determinant for the success of a digital product, it isn’t indispensable for its deployment. I mean, I take into account the UI/UX part in terms of front-end JS/CSS/HTML productions and back-end performances, but I do not strictly consider the ability of design UX patterns or UI elements.