DEV Community 👩‍💻👨‍💻

Zack Philipps
Zack Philipps

Posted on • Originally published at on

How Code Linting Changed My Life

How Code Linting Changed My Life

When it came to linting, I was always dumb about it. "Man that's too annoying, turn it off!" But what I didn't realize was that with 30 seconds of configuration per language, usually in the form of a dotfile in my home folder, I could pick and choose specifically which errors and warnings showed up. So if I don't want to be notified every time a coworker decides to write CSS without a space after the colon, I don't have to. Or if I don't want to be notified that my partial Twig template doesn't start with a <!doctype> declaration... You get the picture.

Now I'm obsessed! There's so much utility in seeing syntax errors as you type as opposed to when the browser refreshes. Linting is another tool that transforms your text editor into an IDE. All the cool kids do it, and it's never too late to start. ...yeah. You can tell I haven't blogged in a while...

Basically, if you use Atom, all you have to do is install the base linter package, and then add your desired languages on top of that. Then, figure out how to configure them to your liking. Enjoy. :)

Related: How I Switched from Sublime Text to Atom

Top comments (0)

Find what you were looking for? Sign up so you can:

🌚 Enable dark mode
🔠 Change your default font
📚 Adjust your experience level to see more relevant content