Frontend Engineering Tools of The Trade
As a Frontend Engineer, I feel tied to my work as my trade, as an artisan creating something both finely tuned in its functionality and beautiful in its aesthetics.
Every craftsman or tradesman has a collection of tools that help to make them better at executing their work. If you're beginning your journey as Frontend Engineer, these are the tools I believe you should add to your collection, both generally the types of tools you'll need and the specific tools I use.
Generally, every Frontend Engineer should know what each of these are and why they're important to use:
- Operating System
- Text Editor
- Command Line Interface
- Package Manager
- Programming Languages
Your operating system (referred to also as environment) is the most foundational tool you'll have. Everything you do stems from the operating system, navigating your file system, editing files, running servers and scripts, all of it happens in the operating system.
There are two types of operating systems you'll use as an engineer:
Local Opreating System This is your development environment. All of your development work happens here.
Remote Operating System This is any environment meant to be available to the outside world. At the very least it will be your "production environment" where your programs will be available to everyone. You could also have the following:
- QA Environment A place to check that your code works, but with mock data.
- Staging Environment A place to check that your code works with production data before it's live as production.
Locally, I use Mac OS X Yosemite (or the most recent stable OS X version), the obvious main reason being that I use a MacBook Air.
Mac OS X at a low level emulates very closely the operating system I use in production, which is very advantageous, because the closer you can be between local and production, the less possible things that can go wrong.
This is becoming less and less of an issue with tooling, such as Docker giving developers the power to isolate their code to a container that will be exactly like production, but I still think it's a good thing to keep your environments as close as possible in their low level systems.
When you start developing for the web, you'll need to push code to production environments. You'll also probably use
ssh to access your production environment to make minor changes to your server. For example, I
ssh into my production server to modify my
nginx configurations for a/b tests and routing.
I use Digital Ocean (referral) to host my production server, and I use the Dokku droplet, which is an application that allows you to deploy your code using a push to
git and a recipe of what to do once your code has been received to the
Your text editor is where you'll spend all your time actually writing code.
I use Sublime Text 3 in
vintage mode (emulates
vim keybindings). Sublime Text has a
package control that allows you to install "plugins" that allow you to be more productive, and I absolutely recommend installing
My Favorite Packages:
- Advanced New Package
- Git Gutter
- Pretty JSON
Installing a package, once you've installed
package control, type
cmd + shift + p and type
install package. Hit enter and type the package name you want to install and
Sublime Text will install it for you. Note: Sometimes you may need to restart
Sublime Text for a package to work.
Getting started with
Sublime Text? There's a great tutorial for the perfect workflow in sublime text on the tutsplus network.
If you're using a command line tool, you should setup the shortcut for opening Sublime Text 3 from the Terminal.
Frontend Engineers spend a huge amount of time reconciling issues between browsers (mostly because of Internet Explorer), so it's good to have a suite of them installed.
If you're on a Mac, you should install Google Chromeand Mozilla Firefox. Safari comes preinstalled. If you're working for a company that requires Internet Explorer support, I'd suggest using a virtual machine and try out Miccrosoft's virtual machine's for the version you need.
I spend my actual development time in Chrome because I am very familiar with, and find a lot of power, in their DevTools. For documentation on getting started with DevTools, checkout the chrome developer guides for DevTools and for a more indepth look into how to use them, check out codeschool.com's free discover devtools course.
Command Line Interface
A Command Line Interface can be really daunting to use, and it could be confusing as to why you should use one in the first place.
When you start working with local development, you'll find yourself running servers, creating directories and files, using
git in your workflow, running scripts, lots of things that will make you productive, but can only really be done in a
I use iTerm2, but lots of people use
Terminal.app which is a core application to Mac OS X.
Installing new languages and new utilities can be a real pain if you have to do it different ways. Package managers allow you use a common language/syntax and convention for installing all of these.
Thankfully for Mac, there's a utility called Homebrew that will allow you to install programs with the same syntax and keep those programs and utilities in a common location.
Programming languages are the heart and soul of your work. Without a programming language, your not programming. There are a few that are core to being a Frontend Engineer and a few that I use to make my workflow easier.
HTML. HTML (Hyper Text Markup Language) is the language of the web. It's the structure and content of how webpages are created.
CSS. CSS (Cascading Style Sheets) is the language of defining how HTML looks and feels. Everything from font-type, colors, layout, borders and (sometimes) animation is defined using CSS.
Git. Git is more of a system than a language, but it's one of the most important tools a developer working in a collaborative environment will use. Not to be confused with github (which is just one of many places to store your git projects),
git is a version control system that allows you to keep a history of all the changes you've made on a project over time and merge multiple user's code into a single "source of truth". When paired with a powerful system, such as Dokku, you can leverage a remote server as a way to both keep your version controlled projects and deploy those projects with a single
GoLang. I started tinkering with Go because it's fast. It's strongly typed, compiled and has lots of support for creating web servers and for cross-platform functionality. I've built a few small utilities for personal use, but I also really like Hugo(a static site generator) and the MongoDB Driver for Go.
Markdown. Markdown is a wonderful way to write in an easy to learn, easy to read, common plain text syntax that is converted into HTML in places like github.com and by static site generators (and some blog platforms). Most documentation (this blog post included!) is written in Markdown, which makes it a really useful language to learn and use. GitHub has great documentation on learning the basics.
Bash. Bash is the language of the terminal. A lot of utilities are written in bash, but I generally only use it for my dotfiles, which includes aliases and mini-functions for executing certain things in the terminal.
The Tools Of The Trade
As a Frontend Engineer, it's important to know why to use certain tools and which tools work best for you. There's no clear cut dogma saying "these are the tools everyone should use", but I believe the ones I've shared are the best tools for me to be most productive.
Are you a Frontend Engineer? What tools do you find valuable (and why)?