The art of committing

While working with Git, committing seems the easiest part of the job: you add files, write a short comment, and then you're done. But it is just for its simplicity that often, especially at the very beginning of your experience, you acquire the bad habit of doing terrible commits: too late, too big, too short, or simply equipped with bad messages.

Now we will take some time to identify possible issues, like unmeaning or too large commits, drawing attention to tips and hints to get rid of those bad habits.

Building the right commit

One of the harder skills to acquire while programming in general is to split the work into small and meaningful tasks.

Too often, I have experienced this scenario: you start to fix a small issue in a file; then you see another piece of code that can be easily improved, even if it's not related to what you are working on now - you can't resist, and you fix it. At the end, and after some time, you find yourself with a ton of concurrent files and...