SODD is not such a bad thing.
If it's been written by someone smart and has a lot of upvotes, it's probably better than most code.
There's an idea there ...
Re:Asshole driven development (2007)
by AnimalMuppet on Friday January 06, 2017 @12:04PM
(#13337944)
It might give you good code, but by piecing together snippets of good code, you're somewhat more likely to wind up with a lousy architecture...
Re:Asshole driven development (2007)
by markatkinson on Friday January 06, 2017 @07:10AM
(#13335697)
I just spat out my coffee. Unfortunately I think PEPDD is more common than we might think.
PEPDD is the reality based term for MVP :)
I'd put money on the proposition SODD could be made to work.
The entire code base must be comprised of purely copy-and-pasted code examples from SO. No typing allowed. This actually may be an interesting challenge!
MIJDD: Machete In Jungle Driven Development.
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".
PEPDD: Prototype Equals Production Driven Development.
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".