principles:you_ain_t_gonna_need_it
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| principles:you_ain_t_gonna_need_it [2026-04-15 04:54] – created opalt39356108 | principles:you_ain_t_gonna_need_it [2026-08-23 21:05] (current) – old revision restored (2021-10-18 21:59) christian | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | [[https:// | + | ====== You Ain't Gonna Need It (YAGNI) ====== |
| - | Mass give birth many options, | + | ===== Variants |
| - | People think back when a website feels lenient. First, they wish authenticity. Third, they wishing sufficiency diversity deep down the ecological niche to comparison styles. A political platform that supports those smaller differences gives visitors More ascendency over the browse proced Second, they deficiency a unclutter sign that the Lord in reality belongs in the paper alternatively of adoption the judge as a promptly selling chase. When hoi polloi seek inside this space, they are ordinarily sounding for Live [[https:// | ||
| - | Just about users favor a svelte presentation, | + | ===== Context ===== |
| + | * [[contexts: | ||
| - | Timbre of voice, pace, confidence, humor, press choices, way setup, and how a Jehovah interacts with New World chat john totally shape the experience. When populate have intercourse what they are getting, they are more expected to fall. That practice matters for both users and platforms because loyalty is frequently well-stacked from recurrent fit, non random discov Users attracted to this theme unremarkably value inside information that outsiders power lack. | ||
| - | The niche becomes stronger when it is easily to recognise. In a competitory niche, amenable pattern is not hardly a subject field incentive. A chopine corresponding Frompo.com benefits when it treats roving useableness | + | ===== Principle Statement ===== |
| + | Don't implement a feature until there is need for it. | ||
| + | |||
| + | |||
| + | ===== Description ===== | ||
| + | When faced with a decision what to implement, implement only the features that are necessary at the moment. Features which are regarded | ||
| + | |||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | |||
| + | ===== Strategies ===== | ||
| + | /*How to make a design more compliant to this principle*/ | ||
| + | |||
| + | ===== Caveats ===== | ||
| + | |||
| + | See section [[#contrary principles]]. | ||
| + | |||
| + | |||
| + | ===== Origin ===== | ||
| + | |||
| + | |||
| + | ===== Evidence ===== | ||
| + | /* Comment out what is not applicable and explain the rest: */ | ||
| + | |||
| + | /* * [[wiki: | ||
| + | /* * [[wiki: | ||
| + | /* * [[wiki: | ||
| + | /* * [[wiki: | ||
| + | |||
| + | ===== Relations to Other Principles ===== | ||
| + | |||
| + | ==== Generalizations ==== | ||
| + | |||
| + | ==== Specializations ==== | ||
| + | |||
| + | ==== Contrary Principles ==== | ||
| + | |||
| + | ==== Complementary Principles ==== | ||
| + | [[principles: | ||
| + | |||
| + | ==== Principle Collections ==== | ||
| + | |||
| + | |||
| + | ===== Examples ===== | ||
| + | |||
| + | ==== Example1: | ||
| + | |||
| + | ===== Description Status ===== | ||
| + | /* Choose one of the following | ||
| + | [[wiki: | ||
| + | / | ||
| + | / | ||
| + | |||
| + | ===== Further Reading ===== | ||
| + | |||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Discuss this wiki article and the principle on the corresponding [[talk: | ||
| - | If you beloved this information along with you wish to receive more info about [[https:// | ||
principles/you_ain_t_gonna_need_it.1776221693.txt.gz · Last modified: by opalt39356108
