On 7/10/07, aslak hellesoy <[EMAIL PROTECTED]> wrote:
> On 7/10/07, Marcus Ahnve <[EMAIL PROTECTED]> wrote:
> > Whether or not to start with the view is a topic of great debate. Many
> > agile luminaries propose waiting with the ui for as long as possible,
> > whereas 37Signals for example won't st
On 7/10/07, Marcus Ahnve <[EMAIL PROTECTED]> wrote:
> Whether or not to start with the view is a topic of great debate. Many
> agile luminaries propose waiting with the ui for as long as possible,
> whereas 37Signals for example won't start coding without a full HTML
> mockup.
>
I wouldn't call my
Whether or not to start with the view is a topic of great debate. Many
agile luminaries propose waiting with the ui for as long as possible,
whereas 37Signals for example won't start coding without a full HTML
mockup.
I've tried all different ways - even starting with the model - but I
agree with
Cool. I'll have to give it a try on my next project.
On 7/6/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On 7/6/07, Jed Hurt <[EMAIL PROTECTED]> wrote:
> > I just read 'Mocks Aren't Stubs' and was intrigued by the notion of
> > 'outside-in' TDD.
> >
> > As a Rails developer, I'm curious if oth
On 7/6/07, Jed Hurt <[EMAIL PROTECTED]> wrote:
> I just read 'Mocks Aren't Stubs' and was intrigued by the notion of
> 'outside-in' TDD.
>
> As a Rails developer, I'm curious if others are employing this method
> when developing Rails applications using RSpec. Is it common practice
> (or even pract
I just read 'Mocks Aren't Stubs' and was intrigued by the notion of
'outside-in' TDD.
As a Rails developer, I'm curious if others are employing this method
when developing Rails applications using RSpec. Is it common practice
(or even practical) to drive the development of a Rails app by
starting
