Hacker News new | past | comments | ask | show | jobs | submit login

This is pretty much an instance of the good old "zero, one, infinity" rule.

http://www.catb.org/jargon/html/Z/Zero-One-Infinity-Rule.htm...




This article restricts itself to a context where following "zero, one, infinity" results in simpler, more concise code. This is a good restriction. In general, following "zero, one, infinity" will often put you at odds with YAGNI.


My experience with Clojure has been that sticking to N is so harmonious with the Clojure way that it is simpler and yields more flexible code.

If the code is simpler then I don't see how YAGNI comes into play. Why would you do something that is both more complicated and less amenable to future needs?


By "in general" I meant outside the context the post was restricted to, i.e. Clojure. What you're saying is the same as what I said in the first part of my comment, up to "This is a good restriction."




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: