Talk:You aren't gonna need it
|This page was nominated for deletion on 27 March 2009 (UTC). The result of the discussion was keep.|
|This is the talk page for discussing improvements to the You aren't gonna need it article.|
|WikiProject Computing / Software|
Aren't or Ain't
Isn't it "You AREN'T Gonna Need It"?
- I once heard that people prefer ain't to aren't, though I don't know why. -- Taku 01:22, Apr 12, 2005 (UTC)
- It would be "You aren't GOING to need it." if you want proper English, but that just doesn't have the same impact.
- Isn't the c2 wiki a definitive source on these terms? It uses the proper english, and I would disagree that the proper english has less impact. Cedear 17:49, 27 February 2007 (UTC)
Appropriateness Of Acronym Components
Jon (talk) 17:06, 19 November 2008 (UTC): I have a hard time accepting the formalization of YAGNI as an industry "philosophy term", not because the philosophy is wrong but because the acronym's components do not reflect the philosophy. The philosophy is "do not add features until you need them", but the acronym says that you already don't need them, which is terribly presumptuous and as such it is prone to abuse by hard-nosed, clueless tech leads and managers who end up demanding a crippled product because features didn't get implemented to begin with. The acronym should instead be something along the lines of "AYGNI", or "Are You [Truly] Gonna Need it?" More here
- Of course there are, c2:DavesRealExampleWhereThinkingAheadWouldHaveHelped and c2:YagniExceptions. -- intgr 16:04, 18 April 2007 (UTC)
I don't believe either of these pages are good counterexamples to YAGNI. As evident by its title, the first page is about a project that did no planning. This is not YAGNI; on the contrary, YAGNI requires planning beforehand so you know what YGN and what YAGN.
Similarly, the other page describes dysfunctional projects that blame YAGNI with no evidence YAGNI was the problem or even used; or implausible hypotheticals like that of a DBA who refuses to implement required functionality but is happy to implement unplanned whims. Clearly, in a case like this, what YAGN is the DBA. Corvus 01:53, 22 July 2007 (UTC)
"A logical conflicting factor is the notion of completeness, which tends to define missing options, or facets, mostly likely to be needed: for example, among features which allow adding items, deleting items, or modifying items, completeness could be used to also recommend "renaming items". The critical impact of completeness can be seen in some types of wiki-collaboration software which can add or delete image-files, but not simply rename images, at all, even after several years of software upgrades."
This should be a very simple decision. YAGNI is a term programmers use, and it has an agreed meaning. Whether you LIKE that meaning is not relevant. This is part of the vocabulary of modern programming and as such should be included in Wikipedia. —Preceding unsigned comment added by 184.108.40.206 (talk) 18:57, 30 March 2009 (UTC)
The Balancing Concerns section does not belong
The point of the article is to define what the term means.
The Balancing Concerns section is editorial in nature, and presents one person's view about whether YAGNI is appropriate. I don't think it belongs in the article.
I agree. It also cites no sources, so I'm adding the "original research" banner. The article should probably just be cut down to the intro paragraph (which has sources) and rewritten based (at least initially) on c2 wiki stuff and Kent Beck's "XP Explained." DuelinMarkers (talk) 18:55, 9 August 2009 (UTC)
Agreeing with Eric. It would be perfectly OK to present criticism of YAGNI in a separate section, but it shouldn't be presented as if it were part of the philosophy. Martijn Meijering (talk) 20:10, 30 April 2010 (UTC)
The article has been in a "POV-challenged state" for a long time, with no prospects of improvement any time soon. I suggest we remove the balancing concerns section altogether, making sure the remainder of the article is properly neutral and descibes YAGNI as a widespread opinion in agile software development circles, not as a generally accepted fact. I say this as a strong supporter of YAGNI. Martijn Meijering (talk) 20:53, 11 February 2011 (UTC)
I've removed it, as WP:OR. If anybody wants to advocate these points (at least some of which are not without merits, BTW - but still original research) - to comply with WP:NOR it is necessary to write an article on it outside Wikipedia and then put a link to it to the talk page (and if in doubt - feel free to ask me where the article can be published - I know a place where a good article on this subject will be welcome). Ipsign (talk) 06:34, 4 February 2012 (UTC)