LazyProgrammer(tm) Development Methodology

So coding came to a halt this weekend, but sunday evening was productive, made a list of top priority issues / bugs that need attention.

Surprisingly the list is only 1 page of A4.

I'm not sure if this is part of any software development methodology, so I'm adding it to my new LazyProgrammer(tm) Development Methodology: -

1) Sit down and in less than a paragraph write what it is you want to achieve. Spend as long as possible researching ways to achieve your goal in as few LOC as possible.
2) Develop a prototype as quickly as possible.
3) Start the official build which is usually an extension of the flakey prototype.
4) 1/3 of the way into the project delete everything you've done.
5) Reimplement the official build in the way it should of been done without all that prototype cruft.
6) Review every hour as to weather you've reached target specified in point (1)
7) You've reached alpha. Now write down a list of things issues and bugs that need to be addressed.
8) Address points in (7).
9) Fin.

I'm especially proud of point (4), how many times have you started a project, just to realise that 1/3 of the way through your efforts. Some Finnish programmer released a library in '95 that would implement 80% of your code with a smattering of key presses.