Introduction
These days, there’s increasing pressure for developers and coders to be able to define themselves as “full-stack”.
This basically means they need to have a “very particular set of skills”, though the skills are a little less cool than in Taken.
Think instead in terms of HTML, CSS, JS, PHP, MySQL, Apache, Linux…
A full-stack developer is practically a one-man/one-woman army when it comes to creating web apps. Can’t do all those things? Then you may have trouble getting an interview with a top employer.
Facebook, for instance, will only (allegedly) hire developers they classify as “full stack” and many others are following suit.
Unfortunately, the list of skills involved in developing web apps only continues to grow.
Today there’s some debate as to whether it’s even possible to be a full stack developer. Even those who “believe” in the full-stack developer will debate the best definition for what that means.
So let’s take a more in-depth look into what the term actually encompasses and how you might achieve that lofty, mythical status…