I learned YAGNI early and used it proudly. It saved me from over engineering, and if I am honest, it also gave me a very convenient way to avoid a few uncomfortable design conversations. After a few systems, rewrites, and more than one “we’ll fix it later” moment, my relationship with YAGNI changed. This is a short, reflective take on where YAGNI genuinely helps, where it quietly hurts, and why thinking ahead is not the same as building ahead.