| 释义 |
- Context
- See also
- References
{{short description|Principle of extreme programming}}"You aren't gonna need it"[ (YAGNI)[3] is a principle of extreme programming (XP) that states a programmer should not add functionality until deemed necessary.][ XP co-founder Ron Jeffries has written: "Always implement things when you actually need them, never when you just foresee that you need them."[5] Other forms of the phrase include "You aren't going to need it"[6][7] and "You ain't gonna need it".[8]] ContextYAGNI is a principle behind the XP practice of "do the simplest thing that could possibly work" (DTSTTCPW).[[3] It is meant to be used in combination with several other practices, such as continuous refactoring, continuous automated unit testing, and continuous integration. Used without continuous refactoring, it could lead to disorganized code and massive rework, known as technical debt. YAGNI's dependency on supporting practices is part of the original definition of XP.] See also- If it ain't broke, don't fix it
- KISS principle
- Don't repeat yourself
- Feature creep
- List of software development philosophies
- Minimum viable product
- MoSCoW method
- Overengineering
- Worse is better
- S.O.L.I.D.
- Unix philosophy
References 1. ^1 2 Object-oriented & classical software engineering, Stephen R. Schach, 2007, 618 pages, p., webpage: [https://books.google.com/books?id=hWwhAQAAIAAJ&q=%22you+aren't+gonna+need+it%22 Book-Google-hWwh], quote: "Two acronyms now associated with extreme programming are YAGNI (you aren't gonna need it) and DTSTTCPW (do the simplest thing that could possibly work)."
2. ^1 {{cite web | url=http://ronjeffries.com/xprog/articles/practices/pracnotneed/ | title= You're NOT gonna need it! | accessdate=2007-11-07|date=April 4, 1998 | author=Ron Jeffries}}
3. ^1 Martin Fowler; Kent Beck (8 July 1999). Refactoring: Improving the Design of Existing Code. Addison-Wesley Professional, 431 pages, p. 68, webpage: [https://books.google.com/books?id=1MsETFPD3I0C&pg=PA68 BGoogle-1M]. {{ISBN|978-0201485677}}. Quote: "you aren't going to need it".
4. ^1 Mary Poppendieck; Tom Poppendieck (2003). Lean Software Development: An Agile Toolkit, p.59, webpage: [https://books.google.com/books?id=hQk4S7asBi4C&pg=PA59 BGoogle-hQ]. Quote: "Kent Beck, Extreme Programming Explained, Chapter 17, uses the acronym YAGNI (You Aren't Going to Need It) for this practice and explains its rationale."
5. ^1 Russ Olsen (2007). Design Patterns in Ruby, p.13, webpage: . {{ISBN|9780321490452}}. Quote: "This design principle comes out of the Extreme Programmingworld and is elegantly summed up by the phrase You Ain't Gonna Need It (YAGNIfor short)."
[1][2][3][4][5]
}} 2 : Software development philosophies|Programming principles |