I’ve written a chrome extension that I’ve named git-praise. It replaces the “Blame” button on github with a “Praise” button. It’s not perfect, but it works.

Pull requests are extremely welcomed. I’d love to see this work on other version control systems that I’m not familiar with like bitbucket, or gitlab. Feel free to submit PR’s for improvements or other new features too! Here is why I wrote it:

Bad code is okay.

“I am, at best, an average programmer.” - Jacob Kaplan-Moss

We all write code that’s terrible - especially when starting out but it definitely doesn’t stop there. Sure I strive to do better - I read books, learn new tips and try to stay current with best practices, but that doesn’t prevent me from occasionally forgetting very simple things and making very large mistakes. The fact is that bad code is unavoidable so, starting now, I’m going to get away from the culture of blame and pointing fingers.

It’s okay to write bad code. In fact, I encourage it. To explain that further, I’m encouraging everyone to write their best code, not to create extensive technical debt. Do the best you can and don’t get discouraged. Most of the bad code you write is you learning and when we’re learning we don’t know the answers yet. Seniors and VP’s are not immune to this. Those who claim they’re “blame-less” (heh) are not sending a healthy message. Describing a developer as either great or terrible leaves no middle ground. Continue to write bad code, continue to learn.

If the only options are to be amazing or terrible, it leads people to believe they must be passionate about their career, that they must think about programming every waking moment of their life. If they take their eye off the ball even for a minute, they will slide right from amazing to terrible again. That leads people to be working crazy hours at work, to be constantly studying programming topics on their own time, and so on. - Jake Edge

As Jake the Dog put it,