Re:Amount of profanity in git commit messages per programmin...
by ZachPruckowski on Tuesday February 22, 2011 @04:57PM
(#2251752)
Yeah, any viable list of swear words has to include "damn" (and derivatives), "hell", and "ass" (and derivatives). I'd even go so far as to say that "crap" and "retard" (and derivatives) are sufficiently unprofessional that they belong on the list.
[ Parent
| on HN ]
Re:Amount of profanity in git commit messages per programmin...
by JonnieCache on Tuesday February 22, 2011 @06:31PM
(#2252098)
Also was fuck searched as a word on its own? Because if you include compound words with fuck you are going to catch a long tail of interesting profanity, especially amongst programmers.
You'd want to whitelist against the Scunthorpe Problem though.
Re:Amount of profanity in git commit messages per programmin...
by reinhardt on Tuesday February 22, 2011 @06:03PM
(#2251996)
Add "wtf" to this list and you match more than 50% of all commit messages ;-)
Re:Amount of profanity in git commit messages per programmin...
by cema on Tuesday February 22, 2011 @09:59PM
(#2252800)
Oh no, wtf is professional terminology, cannot remove.
Re:Amount of profanity in git commit messages per programmin...
by rayval on Tuesday February 22, 2011 @07:23PM
(#2252291)
And if one goes that far, one would have to include variant spellings, because in the heat of the moment of cursing an opaque or broken piece of code, a programmer is likely to froth at the keyboard.
Re:Amount of profanity in git commit messages per programmin...
by president on Tuesday February 22, 2011 @08:05PM
(#2252459)
we may need to implement Levenshtein Distance for this