Git pissed

I agree. I love cursing, but I think it works best in more ephemeral situations. In conversation (spoken, written, or otherwise) it works great but in official records that will be often revisited (whether they are source code comments or commit messages) the cursing will eventually come off as tacky as the emotional context that warranted it is lost in time.

If I am browsing through source from 10 years ago, it may help me if a comment alerts me that "this fucking cockstain of a function broke prod", but really there is no connect between me and the emotion that warranted the profanity. I need more context, otherwise it seems tacky.

(I think that recorded conversation, although not ephemeral, retains the emotional context necessary for profanity to 'work')

it would also get one in trouble at many companies. Anyone's that's ever been through an acquisition will know that due diligence includes code scans - it's highly unprofessional to let cursing into a code base.

k, brb, building a git sarcastic tool

Yes, but statistically that will be mere noise, just like I love love love this algorithm or this algorithm works hand in g love with that other one.

This is probably a homage to the original Linux Kernel Fuck Count[1] which included love in its search.

http://durak.org/sean/pubs/kfc/

I've found out why they build up — it seems that the elves have been ignoring them for years now. Makes no sense, I know, but they've gone back to making shoes overnight. It doesn't matter how many times I write TODO, it never actually gets done unless I do it myself anymore.