Shake the Spaghetti Tree

#:um the Unknowable Methodology

I reckon one top-level principle of dev methodology is that one size does not fit all.

#TODO : post-hoc, write Transmissions initial requirements

Maybe Prompt

I could do with a concise simile to express the dev process I'm using with Transmission. It should combine these :

1. Small, speculative steps
2. Frequent review
3. You Might* Need It (YMNI) : _intentionally* go beyond what is immediately necessary to keep options open
4. Throwing spaghetti at the wall, when it sticks, it's done
5. Shake the tree - to dislodge strands that aren't stuck

avoid premature optimisation -

1. Small, speculative steps

2. Frequent review

3. YMNI - You Might Need It : intentionally go beyond what is immediately necessary to keep options open

4. Throwing spaghetti at the wall, when it sticks, it's done

5. Shake the tree - to dislodge strands that aren't stuck

Experience

execute(data, context) was a mistake

tendency to duplicate functionality

RDF can be very painful

RDF-Ext - there must be a better way!!!!