Shane,
That does help quite a bit. I guess my next question is more of a practical
one. I'm completely sold on the behaviour-first methodology for writing
code, but I'm trying to figure out how to incorporate the Story aspect into
it.
Ignoring the Story framework, I'd simply follow a cycle like this:
1. Write Behaviour
2. Verify Behaviour (fails)
3. Implement Behaviour
4. Verify Behaviour (passes)
5. Repeat
Now, how do I add the Story framework into this cycle? Each story obviously
(at least usually) spans mutliple Behaviours, so it doesn't lend itself to a
nice, tight iteration; it'll take more time than that. If I write the
Stories first, it'll take longer for me to get to a "compilable" state,
right? Hmmm.... maybe that's a bad assumption on my part.
{runs off to look at the Hellbound example ... again}
I have to admit, though, I'm pretty sure I'm not grokking something
fundamental in how the Stories are run - what they are actually *doing*. Is
there a lot of autowiring going on in the Story framework?
Oh, and I apologize if the dev list was the wrong place for these
questions. I realized after I started the thread that they probably
*belong* in the users list. *blush*
Thanks,
Andy
