Just say your profanities aloud and don’t let them make it to version control.
In the first major software system I designed and helped build I was a little too open in my comments. For years after that software had entered sunset I’d still get Slack pings along the lines of: “This looks like a Maximum Derek comment: …” They were all diatribes about whatever was giving me grief when I was writing the code and they would all look perfectly at home in the script for 48 Hours (minus the racial or sexuality slurs).
In my defense we were working with PHP 5.3 at the time.
I grew up in a bit of a sketchy neighborhood and up until my mid 20’s all my jobs were the sort where everybody cursed a lot, plus Finns tend to curse a lot in general.
I absolutely have not kept my cursing out of repositories, although looking at my last work project which had about 33000 lines all in all (maybe 2/3 written by me) when including comments, I was surprised to find it only 4 had “shits” and 6 “fucks”. One line in an example & test file had both:
zap.NewExample().Sugar().Errorw("welp, shit's fucked", "IsBadRequest", IsBadRequest(err), Field(err))and then there’s some comments like
// - turn the unsafe.Pointer into a *[8]byte, allowed due to unsafe pointer fuckery // FIXME: this is just to make cli tool usage easier. It's a horrible fucking hack and should be // nuked from orbit // FIXME: get rid of all this gorilla legacy bullshit. Could start by getting rid of the needless // Interface type
Could be their most used application too https://profanity-im.github.io/
There better be some fucking profanity in the source
