Méthodes de développements alternatives appliquées à nos projets informatiques

Faith Driven Development (FDD)

Alias God-oriented programming (GOP)

Il s'agit d'une méthode de dévelopement qui consiste à ne jamais tester ses dévelopements avant de livrer.
"Tester c'est douter" Ezekiel premier, maître pélerin Pastafariste

Random Driven Development (RDD)

Il s'agit d'une méthode de développement où les choix fonctionnels et techniques sont tous réalisés de façon aléatoire.

Blind Driven Development (BDD)

Alias la méthode de la taupe

• Des spécifications qui tiennent sur un post-it,
• pas de visite usine,
• jamais de livraison intermédiaires.

L'application est livrée en un bloc au bout de 9 mois. Et c'est toujours une surprise qui attend l'équipe au bout du tunnel !

Coder Compiler Comiter (CCC)

Un grand classique et toujours une réussite :

• Coder c'est spécificer
• Compiler c'est tester
• Comiter c'est livrer

Duplicate-Driven-Development (DDD)

Tools Driven Development (TDD)

A ne pas confondre avec Test Driven Development qui est une mauvaise... Car tester c'est douter (Rappel) !

Les choix fonctionnels et techniques sont tous dictés par les outils à la disposition de l'équipe.

Panic Driven Development

Ou technique dite de "l'arrache".

Meeting Driven Development

Les réunions, une alternative au travail

Tourette's Syndrome Driven Development

Some good quotes

• The closer you are to shipping, the dirtier the hacks become,
• Just because the compiler lets you doesn't mean you should,
• Make up acronyms and use them in meetings so your coworkers look stupid when they have to ask what they mean.
• Unit tests are not a replacement for thinking
• Good software is a balance between trying to write code too perfect it'll never ship and code too hacky to maintain
• Who decides to do a Friday deployment deserves to work on the weekend.
• Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing

• There are two ways of constructing a software design: one way is to make it so simple that there are obviously no deficiencies; the other way is to make it so complicated that there are no obvious deficiencies. (C.A.R. Hoare)
• “If debugging is the process of removing software bugs, then programming must be the process of putting them in.”
• Most programmers are about as good at estimating development time as the weather man is predicting the weather.
• When you blindly believe in the compiler, is there really any need for unit tests?
• Deleted code is debugged code
• Good software is a balance between trying to write code too perfect it'll never ship and code too hacky to maintain.

• By doing deployments on Fridays, we give our users two full days to find bugs for us
• “It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration.” - Edsger Dijkstra
• "Real stupidity beats artificial intelligence every time." - Terry Pratchett