5 ms·
>>And if you have good programmers, then readability isn't a problem Hrm, I'd argue against that. I know better programmers than me, whose code I hate to work
by berntb 15y ago
>>And if you have good programmers, then readability isn't a problem
Hrm, I'd argue against that.
I know better programmers than me, whose code I hate to work with. Also for Python.
But you seem to define "good programmer" as someone who also comments and documents, so I guess you're by definition correct. :-)
Edit: Yeah, "itsnotme". The fault is rather the idiot bosses that let the smart idiots get away with it... But with non-idiot bosses, you won't have readability problems in Perl either.
- itsnotme 15y agoHaving good programmers who can't agree on a consistent style is problematic, but good programmers can follow a reasonable style guide, even if they have quibbles about it.
- einhverfr 15y agoYeah, well bad commenters come in three kinds: Those who write too few comments. Those who write too many comments. Those who write the wrong comments. Of course, those are not mutually exclusive.......
- kamaal 15y agoAccording to me good code is what makes the comment unnecessary. And writing such a thing requires understanding many things. And those things are language agnostic. Like some one mentioned in this thread, languages tend to be judged by the quality of code produced by their worst user. For once you can write unreadable code in any language. Even in C and Lisp. In fact there you can create bigger problems and more unreadable code.
- berntb 15y agoYou still needs comments that tell what the content of a code file is supposed to do, no matter how clear the code is. (And in scripting languages which doesn't declare parameters, like Python and old style Perl, you need to document what the parameters are.)