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

Pages: 1-

The source code is the documentation

Name: Anonymous 2011-05-28 3:31

se tittle

Name: Anonymous 2011-05-28 7:05

NO EXCEPTIONS

Name: Anonymous 2011-05-28 8:15

>>1
Yeah. Tell that to Haskell programmers.

Name: Anonymous 2011-05-28 15:12

>>1
Yeah. Tell that to Perl programmers.

Name: Anonymous 2011-05-28 16:14

>>1
Yeah. Tell that to brainfuck programmers.

Name: Anonymous 2011-05-28 17:03

>>5
Yeah. Tell that to doublefuck programmers.

Name: Anonymous 2011-05-28 17:23

Who documents their code in this day and age?

Name: Anonymous 2011-05-28 17:27

Yeah. Tell that to programmers.

Name: Anonymous 2011-05-28 18:10

The Jews are after me

Name: Anonymous 2011-05-28 18:12

The Jews are after me

Name: Anonymous 2011-05-28 23:03

>>7
Any professional programmer. Amateurs don't need to document their code because, well, because they are amateurs.

I still kinda agree with >>1

Documentation is source code, the source code of the automated tests.

IHBT 7/10

Name: Anonymous 2011-05-29 7:15

>>1,11
I generally don't document source code. I generally rely on the system design docs to describe my code function. I document source code whenever I make some sort of design decision that isn't covered by the system design docs (maybe library bugs that need routing around or code hacks or magic numbers).

The source code is the documentation

1 Name: Anonymous 2011-05-28 3:31

2 Name: Anonymous 2011-05-28 7:05

3 Name: Anonymous 2011-05-28 8:15

4 Name: Anonymous 2011-05-28 15:12

5 Name: Anonymous 2011-05-28 16:14

6 Name: Anonymous 2011-05-28 17:03

7 Name: Anonymous 2011-05-28 17:23

8 Name: Anonymous 2011-05-28 17:27

9 Name: Anonymous 2011-05-28 18:10

10 Name: Anonymous 2011-05-28 18:12

11 Name: Anonymous 2011-05-28 23:03

12 Name: Anonymous 2011-05-29 7:15