Hacker News new | past | comments | ask | show | jobs | submit login

Absolutely. I see people saying how "blame" has a terrible name and to use git praise instead. In the end, it's all irrelevant.

If you work in a company/team that has a blame and shame culture, you're going to have a bad time regardless of what the git command is called.




Well, since you have no emotions around it whatsoever, and a large chunk of the rest of us likes praise better than blame, there should be no objection to renaming it, right?

The point is, on a subconscious level, names matter. Calling it praise instead of blame frames the entire issue, and primes a different kind of reaction. It's subtle, yes. The underlying data is the same, yes.

But if a subtle change can make life better - or, at worst, keeps it the same - why not do it?


> If you work in a company/team that has a blame and shame culture, you're going to have a bad time regardless of what the git command is called.

I can confirm this can happen even when only two people in the entire department use git or any form of version control at all. In fact I find it even more likely.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: