Colin Law wrote: > On 8 October 2010 13:47, Marnen Laibow-Koser <[email protected]> > wrote: >>> >> There is the phase of deciding in very general terms what the broad goal >> may come the fact that we want user accounts and a login interface. >> Third step: Users should be able to do the following things from that >> guessing what model classes you'll need, but it's absolutely wrong to be >> Remember, Cucumber scenarios are written in English for a reason: >> (To be fair, user management is simple in most cases and requires a User >> till you actually need to write them. > I think we are just going to have to agree to differ on this one,
I would rather not do that. In general, that's a sign that more discussion is needed, as one or both of us is probably missing something. Certainly I'm learning a lot from this discussion. However, I'm perfectly willing to start a new thread for this. > though in fact I do not think our viewpoints are as far > apart as it might appear from this discussion. Quite probably not. As I think about it more, I do realize that I have a *slight* idea about my model class structure at the time I write my Cucumber stories. But then again, the steps that usually change the most are the explicitly model-related ones (Given a user exists with name: "Fred"...) > I also think that you > have to allow a bit of flexibility in approach for the different ways > that different peoples brains work when analysing a system > requirement. Maybe. I am not at all sure that this is a matter of cognitive style. > Looking back over my career I cannot remember any > instances where I got in a mess or wasted significant time by thinking > about the underlying objects too early in the analysis, Not to be snarky, but would you really know? It's easy to do a premature analysis, get it wrong, and stick with it long after it should have been discarded. I've probably been guilty of this on occasion myself. > but I can > remember instances of problems when I left this phase too late. What sort of problems? In general, leaving it as late as possible seems like the right thing to do. > Of > course the length of my career may have a bearing on what I can and > cannot remember :) :) > > The one thing that I am sure we can agree on is the importance of > making sure that what is provided is what the user wants, not what you > think he aught to want or what his managers thinks he wants. Right. > Provided > we achieve that then slight variations in the route to get there are > not so important. Failing to understand the user requirements is the > principle cause of IT system failures I think. Yes, I would think so, with hacking a close second. > > Regards > > Colin Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
