SODD: Stack Overflow Driven Development.<p>The entire code base must be comprised of purely copy-and-pasted code examples from SO. No typing allowed. This <i>actually</i> may be an interesting challenge!<p>MIJDD: Machete In Jungle Driven Development.<p>Start down an initial path to solve the problem, and then never back-track, turn around, or admit it may be the wrong way despite how many swamps, cliffs or deadly bugs you run into. Also known as "BAWM", or "Burke And Wills Methodology".<p>PEPDD: Prototype Equals Production Driven Development.<p>If an initial attempt at writing the code compiles and seems to do the job, don't worry about debugging or refactoring, just ship it, start charging the customers, and start bolting on new features ASAP. Also known as "Additively Deployed House Of Cards", or "ADHOC".
Fuckit Driven Development; when you're tired of your manager making nonsense decisions and not respecting your expertise so you give up caring and blindly do what they ask in order to avoid arguments.
How about:<p>Despair Driven Development - It's clear the project/company is going to fail anyway, so hack on anything you want, it doesn't really matter.
I work in a monolith driven development environment.<p>The application is now so huge, that rather than reuse code, team members just add new but very similar methods for new features, because you can no longer identify the code you should be reusing/tweaking for that new feature, because it's lost in a sea of shit code and complexity, maintained by multiple developers (some good, some bad, some awful) over the last ten years.<p>Closely tied to Customer Driven Development, where be features get developed because customers are willing to pay for the development, even if the change doesn't make much sense, or is being used to mimic a bad manual customer business process.
And how about Fear Driven Development.<p>It essentially a fear of trying out best technology, or best practices or fear of visibility. situation where organization does not support a progressive environment instead everyone has been kept under some kind of fear or pressure to create shitty code.
ARDD: Ayn Rand Driven Development.<p>Every class does only what's best for itself with no thought or concern given to any other class, any objects created are held on to privately forever and any object that needs something is considered a parasite.
JITD (Just in time development): where you know that you aren't going to get specs that match the data you'll eventually need to parse, so instead of writing the code to do it you just wait until you get the actual data file and then bang out the code to parse it an hour before you're supposed to demo.
TDD (timecard driven development) - hack on shit for a while. commit at 4 PM. you may not be able to separate features, but you can back code out to the most recent "runs" commit before the rollback you need!