In our office, I always take the blame jokingly to lighten the mood. It's a running gag, we have three people who are more senior than the others, and we always say "it's his fault, and if not, it's the other one and if not, then it's Leo's fault" (I am the most senior). When a problem arises, it doesn't matter who inserted the bug, but how to fix it the quickest.
But shaped like this, with the name, the graphics, the "whyyyyy" and the overall implication that the commit author had screwed up, it's indeed hostile and counterproductive.
It lets you find the reason why and context in which certain code was added.
Of course, banter between long-time colleagues is usually harmless. But it's often difficult knowing where to draw the line.
As a tool this would be pointless and unhelpful. A graphic splash that does not explain why the code is bad and how it could be improved. Junior coders would be just shamed while seasoned professionals would be just irritated. Shame and irritation are usually unhelpful emotions.
There's a difference between "curl ... | sh -" and this.
He's even separated it nicely into steps, so you can view that (very short) file in between.
What worries me more is that he doesn't properly quote $@, so this script will break when there are spaces in the filename. One of the reasons I hate bash.
"Don't worry, you don't even need to 'sudo' this so it can't do any harm!" See, it's not running as root while it wipes clean your home folder.
Why do programmers hate other programmers so much? Why do they have so little empathy and care?
Too much staying in one own's head? Lack of exposure to diverse opinions and emotions?
What do you mean?
I think this emerge of a certain way that programmers think of other programers.
There are of course exceptions, but often tools made by other programmers don't seem to respect us as users and have bad user experience: - Few thoughts given to make common operations good, - Lots of clunky menus, - Poor performance,
Basically going out of their ways to make us do something else than programming by killing the feedback loop. (Think libraries that are slow to compile, tools that run slowly or require assistance or are otherwise too granular)
The absolute worst example I can give is something like Hudson or Jenkins.
> cd comment-parser/
> git punish -L1,24 index.js
code and committers you see on the page are parsed out from `git blame`
Otherwise selecting text sometimes results in grabbing the image instead.
It should be a service that mails all other contributors in the commit log something like this: "Mr. <insert name> introduced a CATASTROPHIC security bug right here! Look at that! <insert code> <insert insults> Are all his contributions hidden landmines that might jeopardize the project at any time? Clearly they need to be checked! <insert list of all his other commits>"
Maybe "git shame" would be more appropriate too.
And yeah, you should probably not do that if it's a company project or a noncritical open source project.
