Was ist das Gegenteil von TDD? [geschlossen]

Question

Test Driven Development (TDD) und seine Vorteile sind klar definiert. Das gleiche gilt für Praktiken wie Behavior Driven Development (BDD) gesagt werden. Jeweils eine Software-Entwicklungstechnik, die Befürworter mehr Disziplin, bevor Sie beginnen Codierung.

Was also ist die bequeme Abkürzung für den "unstrukturierte" Ansatz für die Entwicklung?

Ich habe gelegentlich gesehen „TAD“ (Test nach der Entwicklung) verwendet, aber das bedeutet noch Tests durchgeführt wird. Hat jemand gesehen (oder hat jemand möchte erfinden) ein Akronym für den Ansatz für die Entwicklung „-Code es as you go“? Ich suche nach dem TDD / BDD / xDD Äquivalent für die Art der Entwicklung, die wir alle getan haben, wo wir einfach Code schreiben und loslassen.

(Offensichtlich gibt es viel Platz für "Komödie" hier, also lassen Sie uns Refrain von "n00b Driven Development" und der ILK).

[UPDATE]

Viele sehr gute Antworten. Letztendlich denke ich, die Ideen von "Entwicklung Driven Development" oder "Idee Driven Development" beste Antwort der Frage. Wo in TDD Sie versuchen, Tests zu bestehen und in BDD Sie versuchen, das Verhalten gerecht zu werden, in „unstrukturierten“ Entwicklung, sie ist wirklich nur dann angetrieben, indem Sie versuchen zu konvertieren eine Idee, um Code.

Klar, keine richtige oder falsche Antwort, aber eine gute Sammlung von Meinungen hier. Hoffentlich wird diese Ressource nützlich sein für andere versuchen, klar die „Definition“ der Entwicklung in Abwesenheit des Prozesses zu erfassen.

Answer 1

I'd tend to agree with Pavel but would go further and call it:

Development Driven Development

Development driven without any clear motivation is development for the sake of development. In TDD, you develop to satisfy tests. In BDD, you develop to establish some behaviour. In Development-driven development, you develop because you're a developer and that's what you're paid to do.

Answer 2

I don't know about an acronym, but what you're referring to is typically called Cowboy Coding.

Cowboy Coders are programmers who write code according to their own rules.

The Cowboy Way:

• The speed with which I can hack something together determines my worth
• People who need comments in order to understand my code are too dumb to be working with me
• People who ask me questions about my code are too dumb to understand it, and (therefore) are too dumb to be working with me
• Other people's code is just crappy, but mine is self-descriptive and beautiful
• Exploiting a compiler-dependent language feature to save a line of code is "elegant"
• Other people on my team cause all of the bugs; I'm the one that fixes them
• My code is never at fault, always perfect, and I don't make mistakes
• Since my code is never at fault, I don't need to test it thoroughly, if at all
• Since my code is always perfect, it never needs to be refactored no matter how long it's been in the codebase or how much has changed around it
• Since I never make mistakes, I can yell at anyone else who does
• Since my code is perfect, if the program crashes due to unexpected data, it's the user's fault for entering bad data.
• Since my code is perfect, if the program fails after a minor machine configuration change, it's the sysadmins fault for changing it.
• Since my code is perfect, if the program runs too slowly, it's the managements fault for not providing a faster machine.

Answer 3

FDD

Faith Driven Development.

Because you need to pray your project works on every release.

Answer 4

AD(D)D - Attention Deficit (Driven) Development

In which you:

• randomly work on whichever portion of the application attracts your attention at the time
• work on features for whichever user squawks the loudest (until someone else squawks louder)
• run down rabbit trails in the code, forget the path you took to get there, and come out at some completely different place and solving some completely different problem
• "refactor" code by changing its behavior without a solid grasp of what it is actually supposed to do or whether it still works when you are finished - but if it doesn't, you might get around to fixing it if somebody squawks loud enough

Answer 5

MaDD -- Manager Driven Development.

It already takes you longer than you estimated just to code the real product--now you want to spend more time writing tests which never get released?!?!