On Tue, Jan 13, 2009 at 6:14 PM, Mark Wilden <[email protected]> wrote:
> On Tue, Jan 13, 2009 at 7:41 AM, James Byrne <[email protected]> wrote: > >> >> Logins are a pervasive feature of this application and so, rather than >> waste effort on policing the feature syntax, I thought it best just to >> accommodate the likely variations from the start. > > > Premature flexibility is one of the roots of all evil. :) > > Seriously, your code has two types of users. Yes, you should make writing > features easier for biz, but you should also make reading steps easier for > dev. Given that, I like the suggestion of explicitly enumerating the choices > of verbiage. A clear pointer toward that choice is the comment. A comment is > an apology for unclear code. All unclear code should be commented, but > unclear code should be avoided whenever possible. > Another principle that calls for a more rigid Regex: http://domaindrivendesign.org/discussion/messageboardarchive/UbiquitousLanguage.html. Everybody should speak the same language and know what it means. Having 4 different ways of saying the same thing will just add to confusion. Aslak > > All IMO, of course. > > ///ark > > > > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
