I used to think that you were either a web designer or a web developer. Or maybe you were one of those rare unicorns who did both. But either way, you either worked on the design of the site, or the code that made it work.
And then I started seeing all these job listings asking for “front-end developers” or “back-end developers” and even “full stack developers.” What the heck did that mean?
After a little research, I found out that as the Web has grown more complex and as more becomes possible on the Internet, developers have gotten more specialized. And that means instead of developers who do it all, many focus on specific parts of development, whether that’s a specific programming language, framework, or other technical areas of expertise.
Still not sure what that means? Read on for more insight into what front end, back end, and full stack developers each do (and why the lines between them are getting really blurry).
HTML (HyperText Markup Language) is the backbone of the Web. Every website you visit is built with HTML. It takes care of all the structure and content. HTML5 is the current iteration of HTML on the Web, although sites built with older versions still run fine in your browser.
CSS (Cascading Style Sheets) is what controls the way the HTML looks on the page. CSS sets the colors, fonts, background images, and even the way the page is laid out (you can use CSS to arrange the HTML elements on a page however you want, even if it’s different than the order they’re arranged in the HTML file). CSS3 is the current iteration of CSS on the Web and adds a ton of features for things like basic interactivity and animations.
It’s the Internet, what can we say!
While the front end is everything the user interacts with directly, the back end is much more behind-the-scenes and can have some advantages over front-end technologies for specific projects. Back-end programming languages include PHP, Ruby, Python, and more.
One thing to note: You’re probably not going to see many job listings that say a company is looking for a “back-end developer.” Instead, you’ll find listings looking for Ruby developers or PHP developers, etc., because the actual programming language a developer knows is key to being the right fit for a particular job.
Back-end developers generally work with a front-end developer to make their code work within the site’s design (or to tweak that design when necessary) and front end.
As the line between what can be done on the front end vs the back end becomes more and more similar, and as things that were previously only possible on the back end become possible on the front end, more developers are becoming what we call “full stack.” A lot of employers (especially agencies who work on different kinds of sites) are looking for developers who know how to work on all the parts of a site, so they can use the best tools for the job regardless of whether it’s technically “front end” or “back end.”
Now, contrary to what a lot of people think, “full stack” doesn’t necessarily mean a developer is actually writing all of a site’s code themselves. Many full stack developers spend the majority of their time in either the front or back end code of a site.
But the point is that they know enough about the code across the entire stack that they can dive in anywhere if needed. And some full stack developers do code entire websites, including both the front and back end, but usually only if they are working freelance or are the only developer working on a project.
Most full stack developers specialize in a particular back-end programming language, like Ruby or PHP or Python, although some, especially if they’ve been working as a developer for a while, work with more than one. In job listings, you’ll generally see openings for “full stack Ruby developer” or the like.
The great thing about learning Web development is that it’s always changing, so even if you do choose an area, chances are that within a few years what it means to be a “front end” or “back-end” developer will radically change. Learning both front and back-end languages is a great way to make yourself a more valuable, forward-thinking, and versatile developer because it’s not likely that you’ll actually be able to focus exclusively on one or the other.