News for hackers. Stuff that matters.
Re:The Danger of “Simplicity” by rubinelli on Friday November 22, 2019 @10:05AM (#21606147)
It is easy to look back and say, "I should have made this modular," or "I should have isolated that external dependency." It is easier to see how another level of indirection would have saved you work after the fact, but maybe YAGNI was the right call at the time.

That's the trap that Magic and poker players call results-oriented thinking: You got burned once by making the best decision available given the information you had, and you give that experience a disproportionate weight, like the player that lost big with a pair of kings in his hand, and undervalues a pair of kings after that.

Re:The Danger of “Simplicity” by sullyj3 on Saturday November 23, 2019 @03:09AM (#21613032)
When you look back, you're looking back from the particular world where X became a requirement. If instead, Y had become a requirement, you would be looking back wishing you had structured your code in some completely different way. YAGNI then applies to the extent that you can't predict which of X and Y it will be in advance.