Git - Preslav Rachev

The Myth of Code Coverage

One question I often ask potential software engineering candidates is to pinpoint the percentage of code coverage in an ideal project. Interestingly enough, many of them jump to the sky with numbers beyond 90%. They would start preaching how well-tested code is more reliable and brings more value to all

Programming

Use the Git History to Identify Pain Points in Any Project

Have you heard of Adam Tornhill's work? If not, I highly recommend that you set some time aside and check out Your Code as a Crime Scene or Software DEsign X-Rays. In both books, the author dives into a bit of an unexplored territory - looking at the evolution of

Programming

Git Tip: List the Most Recent Branches You Have Been Working On

List and switch back and forth between multiple git branches with ease.

Programming

What’s with the 50/72 rule?

It is part of common sense to assume that the worthiest commit messages lie far from any extremes. Years ago, I often fell in the trap of hastily sending a commit after commit, annoyed by the fact that I have to add a summary to it (let alone a description)