Talk:You ain't gonna need it
From CSSEMediaWiki
(Difference between revisions)
(New page: Added little explanation of the yagni --~~~~) |
|||
| Line 1: | Line 1: | ||
Added little explanation of the yagni --[[User:Dominic Winkler|Dom]] 03:53, 5 August 2008 (UTC) | Added little explanation of the yagni --[[User:Dominic Winkler|Dom]] 03:53, 5 August 2008 (UTC) | ||
| + | |||
| + | Just my two cents: some arguments for YAGNI. | ||
| + | |||
| + | * Nothing is more of a pain than chasing bugs in code that isn't even executing!! | ||
| + | * It keeps the cognitive overhead down when looking at strange code. | ||
| + | * Dead code is not part of the integration-testing loop, so in a test-driven process, it's not valid code. It also tends to fall behind requirements. | ||
| + | * Finally, YAGNI keeps the cognitive overhead down when looking at the code. It self-documents because by it's very existence, it declares what the software actually does. | ||
| + | |||
| + | [[User:Lindsay} Lindsay Kay]] | ||
Revision as of 02:02, 6 October 2008
Added little explanation of the yagni --Dom 03:53, 5 August 2008 (UTC)
Just my two cents: some arguments for YAGNI.
- Nothing is more of a pain than chasing bugs in code that isn't even executing!!
- It keeps the cognitive overhead down when looking at strange code.
- Dead code is not part of the integration-testing loop, so in a test-driven process, it's not valid code. It also tends to fall behind requirements.
- Finally, YAGNI keeps the cognitive overhead down when looking at the code. It self-documents because by it's very existence, it declares what the software actually does.
[[User:Lindsay} Lindsay Kay]]
