I gotta admit, I cringe a little when I see cutesy comments like this in professional code. I see it occasionally in our codebase, through stylecop override justifications "OMG this is the right way" or "// i hate this but whatever"
I'm generally a fan of documenting when you do something and don't like it, though it's generally useful to use something a hair more constructive. At the very least, though, leaving a signifier to future-self or future-non-self that the decision was made as a "least worst option" or a "doesn't matter now, may matter in the future" or otherwise "I don't like this, but doing better is not my immediate problem".
Basically, having any context into why a decision was made is an extremely useful artifact.
Commit history in cowboy projects tends to be really bad.
I've seen a lot of "not so professional" comments in them like:
* empty message
* single word message like "update" or "hack"
* onomatopoeia (arghhh!!!!, yargla!!!!)
* all upper case commit message raging against the company and its lack of recognition