The Ideal JS Developer Environment
This past week I've taken some time to look at my current developer environment and invest a few hours (okay, more like 10) into some better tooling. After spending all that time, I'm relieved and see the benefit already. I think many developers put off looking up good tooling because they're too busy and tell themselves they'll do it later.
That's a bad idea.
The amount of time you will save with the correct environment is worth putting off a new feature for one day.
My setup includes Atom and iTerm 2. I'll be covering the various plugins I use for each. Just a quick note, I have three different macs I have set this up on, and yes I'll go over syncing the config across computers. As a lead developer, you may want to easily share this setup with future employees so their time on-boarding can be as smooth as possible.
Atom
I'll start with the setup I have for atom. Anyone who's used it a while knows it has a fair share of issues. Keeping your plugin count to a minimum keeps it speedy. I onl…
Keep reading with a 7-day free trial
Subscribe to zach.codes to keep reading this post and get 7 days of free access to the full post archives.