lol... Dernière citation de programmeur lue

Always code as if the guy maintaining your code would be a violent psychopath and he knows 
where you live.

Le concept de la métaphore d'Extreme Programming est également un vieux concept

(...)We all know that the only mental tool by means of which a very finite piece of reasoning can cover a myriad cases is called “abstraction”; as a result the effective exploitation of his powers of abstraction must be regarded as one of the most vital activities of a competent programmer. In this connection it might be worth-while to point out that the purpose of abstracting is not to be vague, but to create a new semantic level in which one can be absolutely precise. (...)

Et oui, les 2 derniers post sont tirés de l'article The Humble programmer écrit par Edsger W. Dijkstra en 1972.  C'est fou comme un invente rien...

 

Quiz : qui a écrit ça ?

But: program testing can be a very effective way to show the presence of bugs, but is hopelessly inadequate for showing their absence. The only effective way to raise the confidence level of a program significantly is to give a convincing proof of its correctness. But one should not first make the program and then prove its correctness, because then the requirement of providing the proof would only increase the poor programmer’s burden. On the contrary: the programmer should let correctness proof and program grow hand in hand.

On est pas loin du concept de TDD...

Mise à jour (4 février 2014)

Je viens de lire ceci dans un article sur le TDD :

An early reference to the use of TDD is the NASA Project Mercury in the 1960's (Larman and
Basili 2003).  Je ne suis pas allé vérifier.  Je suis quand même conscient que l'état d'esprit à l'époque était tellement différente que ça n'a probablement rien à voir mais je trouvais ça intéressant de le mentionner.