analyse, esp this one: “People confuse YAGNI with, “We don’t need it right now,” all the time. If there’s one common thread I see among software engineers, it’s that they don’t think long term. They don’t think like an owner of whatever the problem is. Then the stakeholders come back asking for something that an owner would have told you was obviously coming, and they have coded themselves into a wall where a major re-architecture is needed to facilitate that future requirement.”

relation with XP https://www.martinfowler.com/articles/designDead.html

This article provides context about yagni

“Right providing that you imagine the usual development world where the enabling practices of XP aren’t in place. However when the balance between planned and evolutionary design alters, then YAGNI becomes good practice (and only then).”

“The Trip-Packing Dilemma” pdf article by

Transactions

Engineering

Tech Foundations

Title here

Context / Discourse