And because they specifically asked for only one, I code the ui to only
allow one.
Then when a couple years do pass and they ask the question, I say "I'm so
good I can
have this for you in a jiffy" all because I was thinking ahead for them.
Yes. After getting burned on believing users on such things once or twice,
anytime I'm ever asked for a data point that some parent entity "will never
have more than one of", if it's something that is relevant to the purpose
of the system, and it's physically possible for it to have more than one of
it, I design the database and business logic to be able to handle more than
one. It's sooooo much easier and safer to introduce fields or tables into a
database at design-time that one may never use than it is to add them to a
production database in the field.
Sometimes I design the GUI to accept only one, but sometimes I allow a list
of items, and the first time I show it to the user, they say, "Oh yeah,
you're right..." But that's not full-duplex YAGNI; it's YAGNI from the
user's point of view only.
Users often don't know what they want until they see what they can get.
But if it's something that just seems really cool and nifty but unrelated
in any clear way to what the user says they need, I figure YAGNI.
A related term is "gold plating":
http://c2.com/cgi/wiki?GoldPlating
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
