Re:Why is YAGNI a good rule?
by dylangs1030 on Saturday August 24, 2013 @06:45PM
(#6270126)
I divide YAGNI into two cases: security and bloat.
Bloated features are what you just described - more often than not, it's unproductive to code in extra things you don't need on a deadline. You can better work elsewhere. And yet, I think you're right, a lot of developers who will eventually need/want what they're putting in later anyway.
On the other hand, YAGNI has significant security implications. I posted a example downthread about how a database could be compromised by adding in a back-end feature for lazy admins. In that case, YAGNI is really something you want to avoid.
A lean system is an easier system to plug up. But I also understand that's a bit outside the scope of strict features.
Re:Why is YAGNI a good rule?
by Someone on Sunday August 25, 2013 @02:23PM
(#6273021)
For another example where YAGNI is not a good idea, see https://news.ycombinator.com/item?id=6268480 about apps not handling HTTP response code 410 (resource is gone) correctly.
Bloated features are what you just described - more often than not, it's unproductive to code in extra things you don't need on a deadline. You can better work elsewhere. And yet, I think you're right, a lot of developers who will eventually need/want what they're putting in later anyway.
On the other hand, YAGNI has significant security implications. I posted a example downthread about how a database could be compromised by adding in a back-end feature for lazy admins. In that case, YAGNI is really something you want to avoid.
A lean system is an easier system to plug up. But I also understand that's a bit outside the scope of strict features.