3 ms·
I think an important point is that the programmer recognized that what he/she was doing was an ugly hack, (presumably under some serious constraint, like time)
by blogimus 18y ago
I think an important point is that the programmer recognized that what he/she was doing was an ugly hack, (presumably under some serious constraint, like time) and felt compelled to point this out.
A mediocre programmer might come up with the same fix, but not recognize that the fix was an ugly hack, and not comment as such.
- frossie 18y agoI agree with the OP that this is a positive sign. The only thing that surprises me it that it seems to be a free-format arrangement of a word that can be used in a positive way. We have a magic comment word ("kludge", if you must know) that we use for code that we wish we had time to write better; that in principle allows us to go back and find things to fix after the fact, or helps troubleshooting since kludges are more likely to break.
- blogimus 18y agoI'm not terribly creative with code I write for others. Since I've been doing a lot of Java recently, using Eclipse, I stick with // TODO: Which has the added benefit (in Eclipse) of creating a tiny blue box in the vertical source error/warning/status bar (I'm not sure what it's official name is) so I have a visual cue to see where I have unfinished business (Kludges are unfinished business that you might get to next day or never, but even if it's a glorious hack, if you think its a hack and not a "proper" way to do it, its still unfinished business. In a prior project we used to use "glorious hack" as a special comment to use as the first places to investigate when something broke.