Finding comments in legacy code like "too tired, fuck you" or "this implementation is dirtyyyyyy" makes me wanna punch a dev.

I haven't had the need to do it personally, but I don't hate seeing comments that an implementation is dirty.

Sometimes a fix needs to go out fast, and fixing it the proper way takes too long. Also not worth the time investment if you got future plans to rewrite or toss the current implementation.

EDIT: the first mentioned comment is tilting tho, haven't experienced it myself yet.

@bertyboi in general I absolutely agree, but to emphasize my point, the original phrasing was "this implementation is fuKken dirtyyyyyy chicka pow powww" :(

@waitwhat ahh, that does make a difference. The ones I have seen have been like "This implementation is dirty because [explanation], but I do it because [explanation]"

I've written things like:

until (line = get_next()).nil? do // oof. What a travesty.

It's a bad (good?) Habit from my years of C, but looks wrong and alien in Ruby.

A former colleague left code that would have been improved by a few such comments.

At least you would know he knew it was bad. But no, he kept doing the same stupid stuff for 5 years until my boss finally called him out and he quit.