Meh, the "YAGNI" citation by @dhh is pretty weak IMO. YAGNI is a guideline, a heuristic, not an absolute inviolable law of nature. And that's what experience buys you as a developer: the wisdom and insight to anticipate things that are likely to be needed, and places where code should be structured a certain way now, to accommodate future changes.
What we need is a new acronym (well, maybe somebody has probably already coined it, but whatever) YPNGTNI: You're Probably Not Going To Need It.