Should one programmer document other code?

Some of our lead developers chased the manual to appoint a junior developer to document their code for them.

Their arguments are:

  • You will have two programmers familiar with everything.
  • This is a couple programming, kinda.
  • This is more cost effective = they will do more.
  • It demonstrates that their code is readable and supported.
  • They will be happy to answer any questions; so this is a form of mentoring.

However, the number of programmers that they continue to be busy to stay up to date increases with time.

Is that a good idea?


Wow! This is not our experience!

Here are some clarifications that will prove important.

  • - . . " ".

  • ( , , ).

  • , . , .

  • , , , . , YAGNI, .. . , . ( , . - , , - , .)

  • ?

  • Agile " ". , .

, - , , , , . ?

, , , . . ( 3 .)

+5
11

, . :

  • , , "" . . .

  • , ? , , , .

  • - , , , . . , . , , .

  • "". , Javadoc .., , ( ..). , .

  • " " . 5 5 , 5 , . 10 2/3, (~ 6 ).

+13

. - , , - , .

, .

. , 6 , , , ( ) .

, . , - . , .

+4

,

, , , .

, .

+2

!! , , , ?

( ), , , , , , , , , .

? SQA?

+2

- , , , / . , , . , . , - - - .

, - , , , "" . , , , , .

+2

, . , . , , (, ), , .

, . , , .

+1

. . , , . - , . , , .

+1

, , :

Joel :

, CS, , " QA, ". . , , .

, , , , , . -, , , , , .

Yegge :

UW, , , Intel, , . , , Intel " ". , 5 6 , , ; TPS, . , , .

, , , , , - . , . . . UW, , , CS Intel. Intel - , .

, , ... . , , , .

, , /, Google, , , , . ( -, .) , Google, , .

+1

, , .

+1

, -, . , :

  • , ? , , , , .
  • ? , , , .
0

"", , . , , . , , (.. , ). , , ( ) .

0

All Articles