Introducing Chaos Driven Development
[via NiKo]
I should pattent the CDD methodology: Chaos Driven Development
A quick search doesn't show anything valuable...
Hereby I'd propose these guidelines for anyone who wants to dive into CDD method:
- Specifications should be written by throwing small rubber balls on a keyboard linked to a text editor. You may want to continuously repeat this for a week or so. Then you can give the result to a blind person - I'm pretty sure disabled people can enjoy CDD too.
- These specs may now be cut in small tasks by the "project manager" - or, as we name him in CDD, the "M.O.R.O.N.", i.e. Manager Of Relationships Out of Nowhere)
- Each task may be assigned a priority. This is being randomly chosen by an innocent hand, or more precisely the innocent pad of a Schrödinger cat. If the cas dies, the task priority is low. If he's alive, the task is critical.
- The CDD now enter the scene. They must work as pentanomes (group of 5 people): the first one types on the vowels on the keyboard, the second one hits the consonants, the third one takes care of non-alphabetical characters (spaces, commas, digits, etc), the fourth dictates the code to the others, while the last one is been given the task to jump on the keyboard from time to time to add entropy to the system.
- for each task, you must assign, five pentanomes (yeah, the number 5 is cult in CDD, it's so "dada"). These groups are writing code at the same time, on the same working copy, confusing each other's code.
- No need to say, test-driven methodologies are banned. No-one should never ever test the programs. Especially the developers or the customer.
- The software produced may now be shipped via email, to a randomly-generated-email-address generated by a cosmic-background-powered-generator.
For more efficient results, you can move as close as possible from the LHC.