We should automate our development process whenever possible. But there are so many tools available and new ones are published every week. Even though these tools help us, it could be very time consuming to learn and to handle all of these tools.
In this post I’ll show you how to automate development process using only Atom packages.
In recent articles about Atom, I’ve talked about different packages that could help us make our daily jobs easier. Many of those packages have different keybindings. But what happens when a keybinding is already used by some other package?
In this tutorial I’ll show you how you could fix this.
Lint, linter, linting? What is it and why you should use it? I’ll try to show you how Atom linter packages could save you a lot of development time.
I’ve been using all kind of local server solutions back in a day, from WampServer to Vagrant. I noticed that I had to spend large amount of time on learning and configuration. That was, not only time consuming, but also very frustrating, especially when you’re a newby and you don’t understand half of the instructions and problems.
One of the most popular features for Atom out there is a minimap. It’s a code preview in a small sidebar window.
Developers often rely on a version control system and one of the most popular is Git.
This is the first article in a series about my perfect Atom setup. First topic is installation and initial setup.
Powered by Starter Project.