Sexy New Development Methodology!
secretGeek .:dotnuts about dotnet:.
home .: about .: sign up .: sitemap .: secretGeek RSS

Sexy New Development Methodology!

(This was going to be a joke... but now I suspect I might actually be serious!?)

Forget Test-Driven Development!

Try:

TODO-Driven Development!

Here's the process: (continued....)




Comments disabled due to spam.



'jasony' on Sat, 05 Aug 2006 01:56:17 GMT, writes:

Actually, throw stack ranking into this and you have a decent methodology that has high visibility and accessability to management...



'Kim Forota' on Wed, 02 Aug 2006 12:01:13 GMT, writes:

Tis is nice!

URL: http://zimebe.itunisie.com/



'Robert Wang' on Wed, 29 Jun 2005 11:10:59 GMT, writes:

Amazing! I have been using this method to develop fractions of code. very practical, never thought it could be called a methodology though :-)



'vqp' on Mon, 17 Jan 2005 18:09:42 GMT, writes:

It's very similar to my own method, with the only difference that the actual code is done by other persons in my case (I'm a Lord and I have a bunch of code-slaves)

This way, I get all the fun and the code-slaves have to deal with the progrems

a little late for this post, but I think that it worths it



'Dan North' on Mon, 14 Jun 2004 13:44:15 GMT, writes:

I wonder if I can claim prior art?

A couple of years ago I introduced this on a client project, in the form of Comment-Driven Testing. So in my (Java) TDD test, I would have something like:

public void testShouldFindCustomer() {
// create a customer

// look up customer

// verify customer was found
}

Then simply fill out the blanks. I found it much more useful in the tests (where I was making up new behaviour) than in the code itself (where I was simply getting the test to pass).

This has survived into my current (Java) testing template, which looks like this:

public void testShouldDoSomething() {
// setup

// execute

// verify
}

(with the "DoSomething" bit selected for editing).

I still use comment-driven testing when I am trying out different ideas, and I find it is often enlightening to be decoupled from the programming language whilst I try to decide what the system needs to do next.





'secretGeek' on Wed, 09 Jun 2004 05:02:42 GMT, sez:

yep, nobuddy -- it is an example of stepwise refinement!

here's a Nicklaus Wirth article on Stepwise Refinement, from 1971:

http://www.acm.org/classics/dec95/




'nobuddy' on Wed, 09 Jun 2004 04:41:21 GMT, sez:

This is stepwise refinement.



'Aaron Robinson' on Wed, 09 Jun 2004 00:12:19 GMT, sez:

Via Slashdot this evening... it looks like Microsoft has patented your new development methodology. ;)

http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=6,748,582


'Mitch Denny' on Mon, 07 Jun 2004 04:59:29 GMT, writes:

You are my hero.

URL: http://notgartner.com



'Josh Baltzell' on Sun, 06 Jun 2004 13:02:03 GMT, writes:

Even one of the idiots at community college told me to comment first.

I code almost exactly the way you are describing, I'm not all that sure if anyone told me to do it like that, but I think it is helpful to think about the problem with pseudo code before writing a bunch of junk code.

URL: http://shortdomainname.com



'Roy Osherove' on Fri, 04 Jun 2004 14:44:06 GMT, writes:

If "Paper Prototyping" made it, so can this :)

URL: http://www.iserializable.com



'Dominic Cronin' on Fri, 04 Jun 2004 06:03:53 GMT, writes:

Isn't that just XP?



'haacked' on Fri, 04 Jun 2004 03:46:51 GMT, writes:

This is a tool supported version of the guidelines Steve McConnel gives in Code Complete! ;)

He basically says to write pseudocode with comments and then start implementing the code underneath the comments.

URL: http://haack.org


Back to Sexy New Development Methodology!

Articles

TimeSnapper 3.2: What are you afraid of? TimeSnapper 3.2: What are you afraid of?
Babbage and Boole! Babbage and Boole!
Downloadable Slide-decks: Downloadable Slide-decks: "Build your own Tiny Software Company"/"F# eye for the C# guy"
Simple Trouble Shooting Application Now Fixes Everything Simple Trouble Shooting Application Now Fixes Everything
a simple checklist for trouble-shooting regular problems a simple checklist for trouble-shooting regular problems
secretGeek at Tech-Ed: secretGeek at Tech-Ed: "How to build your own Tiny Software Company"
Bambrick versus Hanselman: Bring it! Bambrick versus Hanselman: Bring it!

Archives .: secretGeek :: Complete Archives :.
25 steps for building a Micro-ISV 25 steps for building a Micro-ISV
3 minute guides -- babysteps in new technologies: powershell, JSON, watir, F# 3 Minute Guide Series
Top 10 SecretGeek articles Top 10 SecretGeek articles

Downloads

TimeSnapper -- Automated Screenshot Journal TimeSnapper.com    
Version 3.1: instant productivity profiles

ShinyPower (help with Powershell) ShinyPower
Now at CodePlex

Next Action NextAction
Managing the top of your mind



[powered by Google] 


World's Simplest Code Generator (html edition) World's Simplest Code Generator
Gradient Maker -- a tool for making background images that blend from one colour to another. Forget photoshop, this is the bomb. Gradient Maker
How to be depressed How to be depressed
You are not inadequate.



Recommended Reading

The Best Software Writing I
The Business Of Software (Eric Sink)

Recommended blogs

Jeff Atwood
Reginald Braithwaite
Joseph Cooney
Phil Haack
Scott Hanselman
Julia Lerman
Joel Pobar
Eric Sink
Joel Spolsky
Des Traynor

Aggregated Links

programming.reddit.com
dzone
dot net kicks

Human Link Machines

interesting finds
a continuous learner's weblog
arjan's world
n links today
new and notable
morning coffee
learning .net
weekly link post
(my del.icio.us account)

LinkedIn profile
 
home .: about .: sign up .: sitemap .: secretGeek RSS .: © Leon Bambrick 2003 .: privacy

home .: about .: sign up .: sitemap .: RSS .: © Leon Bambrick 2003 .: privacy