Sublime Text

A text editor is at the heart of a developer’s workflow. I use a few, but Sublime Text 3 is my primary editor and has been since 2012. At the time, I was using Eclipse, a very robust IDE (Integrated Development Environment). One of the developers I worked with was using Sublime Text, so I downloaded a trial and that was that. Eclipse is a great system, but Sublime Text feels better.

What made me jump ship form Eclipse was how well-thought out Sublime Text is and its core features. What continues to make Sublime Text my “go to” editor is the staggering number of plugins and customizations available for it. You can pretty much configure it into something unrecognizable from its “out of the box” state.

The good and bad of Sublime text

There are some parts of Sublime Text that frustrate new users. It’s not necessarily the easiest to configure (you have to edit JSON config files a lot of times) and the number of plugin options can be overwhelming. I look at Sublime Text not as a destination, but a path to get better code. It takes time to figure out what you want and don’t want in your editor, but for me it’s been worth it. I revisit my configuration with regularity and always make a few adjustments.

Some tools you just use, and others get honed with age into something better than what they started out as. Sublime Text is one of my tools that continuously gets updated and made better. I don’t feel any computer I use is  If you write code, check it out.

Sublime Text logo

Leave a Comment

You must be logged in to post a comment.