Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Cleanliness

Name: Anonymous 2010-06-12 23:06

I'm a C programmer by training, and 80% of my work thus far has been in C, but I've recently been put on a project at work that is primarily written in Java and Python.
I immediately noticed that the programmers on this new project write much cleaner source code than the programmers on my last project.  The comments (docstrings/javadocs) are thorough and well maintained, the classes are well organized (the C code usually felt "hacked together" rather than designed, even if that wasn't the case), and the function names actually mean something (no f() or do_the_thing()).
Is this a function of the respective languages, or the "type of people" drawn to the respective languages, or merely a coincidence?
Has anyone had similar or conflicting experiences?

Also, please don't let this turn into a "my language is better than your language" argument or a "my language can do X" pissing contest -- keep it to the topic at hand, please.

Name: Anonymous 2010-06-12 23:13

Skilled Java and FIOC programmers?
Lies.

Name: Anonymous 2010-06-12 23:15

NO EXCEPTIONS

Name: Anonymous 2010-06-12 23:15

>>2
I didn't say they were skilled -- their are plenty of bugs in their output -- but the code looks neater.

Name: Anonymous 2010-06-12 23:15

>>4
s/their/there/

Name: Anonymous 2010-06-12 23:54

>>1
This is a function of you sucking at C.

Name: Anonymous 2010-06-13 0:00

>>6
nobody asked you

Name: Anonymous 2010-06-13 0:02

>>7
A damnable lie.

Name: Anonymous 2010-06-13 0:40

I would guess that it's coincidence. Some languages make it possible to write cleaner code, but it's possible to write shit code in any language.

Name: Anonymous 2010-06-13 10:18

>>9
Not Factor.

Factor makes you write better code.

Name: Anonymous 2010-06-13 10:34

The goal is not clean code but simple code.

Name: Anonymous 2010-06-13 10:51

>>11
Not all code can be simple; all code can be clean.  Simple code is by nature (but not in all cases) clean -- I've seen some elementary programs with nasty code.  Perhaps the goal is simple code when possible, clean code always.

It's inevitable that on any large project, you'll have a bad code monkey or two.  We may not be able to teach them to be good coders, but at least we can teach them to write clean code and hope that it makes obvious their intentions so that we can fix it quickly and not waste time thinking, "what was he trying to do?!"

Name: Anonymous 2010-06-13 13:12

>>10
That is the opposite of true, I'm certain of it.

Name: Anonymous 2010-06-13 17:42

>>13
Slava said it, so it must be true!

Name: Anonymous 2010-12-27 0:27

Don't change these.
Name: Email:
Entire Thread Thread List