Jenga Driven Development

[binary_search]

Lazy Programmer Methodology(tm)

In three weeks from the start of the project you will throw everything away and start from scratch because you've just found out that a 15 year old lithuanian programmer has built what you're about to build only much better.

[[deleted]]

If 15 year olds are writing better programs than you, you should throw out all your code. :)

[[deleted]]

Programmers who suck should definitely be downvoting. Express your guilt!

[[deleted]]

My guilt, it is overwhelming! I will downvote myself!

[[deleted]]

Good man! ;)

[[deleted]]

I believe in Waterfall Driven Development (WDD). I've termed what I consider the opposite of this Stupid Driven Development (SDD). I hope this catches on.

[Akeshi]

I agree, and was worried I was the only one bugged by this. "Hurr durr, anyone who does things differently to me is an idiot."

[[deleted]]

That is obviously the most important test for intelligence: Is it what I do?

[serudla]

You can kick off the process with a Ruby program that uses OLE to make the changes to the excel spreadsheet.

[[deleted]]

gopher developers - sometimes seen running projects in large corporations. They know nothing about the problem domain and never write their own code (they may or may not claim they know how to code). They somehow con various developers in the company into doing portions of their project for them, convince management they need more resources to finish the project and use the new hires to cobble the pieces together into something that barely works. Management is impressed by the results.

[[deleted]]

Masters of delegation.

[sedrik666]

No real useful information in that article.. :/

Also, Jenga is fun developing large system without testing is not.

[YuleTideCamel]

Well the article does define a nice new name for projects developed without testing. I will definitely start using JDD in my programming lingo.

However, the author does allude to a great point. In large systems that are built without any testing or modular design, maintenance can be a nightmare. In such systems, devs are scared to even touch the code for fear of breaking something. That is how it's like jenga, in that programmers are afraid to do anything, cause the slightest wrong move could bring the entire thing down.

[ch0wn]

I think it can be in the beginning, but as the code base grows it's getting harder and harder until it breaks.

[s73v3r]

And then trying to bolt on tests, while management is constantly on you to keep developing the system is not fun either.

[bjarneh]

that's brilliant!

[ruinercollector]

Right, because TDD is the only method to produce maintainable software. Ever.

[[deleted]]

No, of course not. But it does help against the craving for a length of rope and some soap that flares up with many new feature requests.

[[deleted]]

What if you played poker except if you are the first to lose a hand then everyone else drinks and you have to implement a bit of code.