There are multiple reasons people comment code, but one of them is the (often unacknowledged) feeling that they're not using a powerful enough language. Such comments are in effect language design bug reports, and could be a source of ideas about how to make languages better.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The more comments, the better. So, still torturing the kids?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Can you share a code sample? :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I still do this in Python. But much less in Fortran, Mathematica, etc. For me seems like the verbosity of the language correlates with length of comments.
-
“Verbosity”? I do observe a dangerous trend to regard one-liners as the ultimative yard stock to evaluate code “DSLism” .... a powerful language allows you to express yourself with the right amount of symbols ... and complex problems might need a lot of symbols
- Show replies
New conversation -
-
-
Why? Are you going to send him back in time?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Meta boiler plate ....
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I personally prefer coding style that doesn't use comments. The idea is to use really good variable names and maybe a few extra lines to show simply what the code does. Of course some languages might be just too hard to read no matter how much you do refactoring.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Is he permitted to use GOTO?
-
You can't get anything done in Basic without goto.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.