Skip to main content
9 events
when toggle format what by license comment
Jun 4, 2011 at 21:24 history made wiki Post Made Community Wiki by Bobby Tables
Jan 22, 2010 at 22:00 comment added dsimcha Great point. YAGNI is a good philosophy for stuff that there's at least a decent chance you'll never need, not for stuff you clearly will need, just not right this second.
Jan 22, 2010 at 21:51 comment added 80x24 console Stephan, the example shows a glib and inappropriate abuse of the catch-phrase, which was my point. DRY (with its variant OAOO) is also a good principle, but quite separate: c2.com/cgi/wiki?OaooBalancesYagni. However, I cannot find anything anywhere to support your claim that "DRY is a part of YAGNI." Mustard goes well with hotdogs, but that doesn't mean mustard is a part of hotdogs. If you could clarify, perhaps with references, perhaps I will understand.
Jan 18, 2010 at 19:56 comment added Stephan Eggermont That example is not YAGNI at all. DRY is part of YAGNI, and without it you cannot stay responsive to change.
Oct 1, 2009 at 17:02 comment added Min Catch phrase abuse is particularly easy to succumb to. Everyone at my work talks about "Best Practices" as if they're so easy to pin down. I have to remind them that "Best Practices" really means "Practices that work well with these assumptions" (much like everything else in life).
Oct 1, 2009 at 13:58 comment added finnw So you think you should have spent the 2 weeks upfront?
Sep 25, 2009 at 15:25 comment added Fred ^yep, I'd rather deal with YAGNI than that crap.
Sep 25, 2009 at 9:56 comment added Benjol Yes and no, can you predict in what direction it's going to change? I have experience of painfully complex systems which proved totally inadequate for the first reuse, which didn't fit into the predicted genericity...
Sep 24, 2009 at 21:49 history answered 80x24 console CC BY-SA 2.5