On Fri, Nov 30, 2012 at 3:30 PM, Norm S.
[email protected] wrote:
On 11/30/2012 05:22 AM, Dylan Keys wrote:
Users could then register an account book and pay for course utilizing
“Ruby on Rails: Talk” group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
For more options, visit https://groups.google.com/groups/opt_out.
So, I’m going to get my plug in here for “Behaviour Driven Development”.
Start with the sorts of things you want your application users to be
doing. You have a brief start there: register, book, pay, etc, but
there’s obviously much more.
When you have a reasonable set of stories, aka scenarioes, you can
start to write up your features a la cucumber/gherkin and use them to
drive your development, following the red/green/refactor concept in
BigDesignUpFront followed by DoTheSimplestThingYouCanThinkOf is
typically the way to go. In addition, building the application from
the core stories out works best, keeping in mind that you always want
to have a working application, even if it’s just very minimal set of
features. (Pragmatic Programmer calls this “Firing Tracer Bullets”).