User:Berniemonette/Full stack web developer
 | This is not a Wikipedia article: It is an individual user's work-in-progress page, and may be incomplete and/or unreliable. For guidance on developing this draft, see Wikipedia:So you made a userspace draft. Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Full Stack Web Developer
The "stacks" for this term come from the backend and the front end of a Web site. The backend is the database, the server, and the code that joins the two. For example we would see the use of MySQL as the database, Apache as the server and PHP as the code that joins them. Since this group of software usually resides on the Linux operating system this has been called the LAMP stack. On the front end we would typically see HTML, CSS, and Javascript as the main coding technologies that creates the "page" the visitor to the Web site would see.
Source of the term "full stack"
This may be apocryphal but within the Web Development world the source of the term "full stack" came from an article by Carlos Bueno on Facebook called "The Full Stack Part 1" [1]. He talks about the full stack developer as a "generalist" and because of that broad way of seeing the application can "see" how the application works along the stack. He also makes a reference to another article on forge38.com which is no longer available. He goes on to explain: " People who develop broad skills also tend to develop a good mental model of how different layers of a system behave. This turns out to be especially valuable for performance & optimization work. No one can know everything about everything, but you should be able to visualize what happens up and down the stack as an application does its thing."[2]