Programmare senza ego: linee guida

 

  1. Renditi conto che commetterai degli errori e accettalo.
    The point is to find them early, before they make it into production. Fortunately, except for the few of us developing rocket guidance software at JPL, mistakes are rarely fatal in our industry, so we can, and should, learn, laugh, and move on.

  2. Non sei il codice che scrivi, ne quello che hai scritto ne quello che scriverai
    Remember that the entire point of a review is to find problems, and problems will be found. Don't take it personally when one is uncovered.

  3. Non importa quante mosse di "karate" conosci, c'è sempre qulcuno che ne conoscerà di più.
    Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it's not needed.

  4. Non gettare e riscrivere del codice senza confrontarti con qualcuno.
    There's a fine line between "fixing code" and "rewriting code." Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer.

  5. Con chi è meno esperto di te comportati con rispetto, pazienza e con un po di riguardo.
    Nontechnical people who deal with developers on a regular basis almost universally hold the opinion that we are prima donnas at best and crybabies at worst. Don't reinforce this stereotype with anger and impatience.

  6. L'unica costante nel mondo è il cambiamento. (Con buona pace di Eraclito e Parmenide) 
    Be open to it and accept it with a smile. Look at each change to your requirements, platform, or tool as a new challenge, not as some serious inconvenience to be fought.

  7. L'autorità vera deriva dalla conoscenza, non dalla posizione.
    Knowledge engenders authority, and authority engenders respect—so if you want respect in an egoless environment, cultivate knowledge.

  8. Combatti per ciò in cui credi. ma accetta con garbo le sconfitte.
    Understand that sometimes your ideas will be overruled. Even if you do turn out to be right, don't take revenge or say, "I told you so" more than a few times at most, and don't make your dearly departed idea a martyr or rallying cry.

  9. Non fare l'eremita alla tastiera.
    Don't be the guy coding in the dark office emerging only to buy cola. The guy in the room is out of touch, out of sight, and out of control and has no place in an open, collaborative environment.

  10. Critica il codice al posto delle persone - si gentile con il programmatore, non col codice.
    As much as possible, make all of your comments positive and oriented to improving the code. Relate comments to local standards, program specs, increased performance, etc.

Fonte: http://builder.com.com/5100-6404-1045782.html
Segnalato da Adrianhttp://www.furl.net/members/adrianflorea

 

Aggiornamento del 25-Lug-2006

Riferimenti bibliografici: G. Weinberg, The Psychology of Computer Programming, 1971, Ed. Van Nostrand


                                                     

Tags :   |  |  |

Print | posted @ Sunday, June 18, 2006 9:10 PM

Comments on this entry:

Gravatar # re: Programmare senza ego: linee guida
by PierG at 6/19/2006 10:32 AM

BELLISSIMO POST!
PierG
P.S. Luka .... mettilo sul wiki (il nostro :) )
Gravatar # re: Programmare senza ego: linee guida
by Stefano Grevi at 6/19/2006 10:34 AM

Da diffondere presso colleghi ed amici al posto delle catene di S.Antonio.

Gravatar # re: Programmare senza ego: linee guida
by Mauro at 6/19/2006 12:54 PM

Sarebbe da diffondere sopratutto ai nostri datori di lavoro/clienti ;-)
bye
Comments have been closed on this topic.