Talk:You aren't gonna need it: Difference between revisions

Content deleted Content added

Inline

Revision as of 17:07, 19 November 2008

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

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)[reply]

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?"[reply]

Good Aspects

Isn't there at least a good aspect in this philosophy? —Preceding unsigned comment added by Theups (talk • contribs)

No, there is none whatsoever. —Preceding unsigned comment added by 209.17.128.161 (talk)

Of course there are, c2:DavesRealExampleWhereThinkingAheadWouldHaveHelped and c2:YagniExceptions. -- intgr 16:04, 18 April 2007 (UTC)[reply]

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)[reply]

Occam's Razor

This should be related to Occam's Razor. Metaxal 22:50, 21 July 2007 (UTC)[reply]

Ouch

"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."

I wonder what wiki engine they are referring to? :-) Tbsdy lives (formerly Ta bu shi da yu) ^talk 13:17, 6 October 2008 (UTC)[reply]

@@ Line 10: / Line 10: @@
 == Appropriateness Of Acronym Components ==
-[[User:Stimpy77|Jon]] ([[User talk:Stimpy77|talk]]) 17:06, 19 November 2008 (UTC): I have a hard time accepting the formalization of YAGNI as an industry philosophy, 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?"
+[[User:Stimpy77|Jon]] ([[User talk:Stimpy77|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?"
 == Good Aspects ==