This reads more like a novel than a manifesto, but the gist is good. I think the name is misleading too, which doesn't help when you're trumpeting a manifesto.

This reads more like a novel than a manifesto, but the gist is good. I think the name is misleading too, which doesn't help when you're trumpeting a manifesto. When I read 'Code for Flexibility' I hear the antithesis of 'YAGNI', and think of large Java projects where every class implements interface and every interface has one and only one implementation. Yech. The article makes some good points though, that could benefit from a restating. "This too, shall change" might be a good mantra for those writing software in almost all environments. "Don't get too attached" speaks more to me than "Code for Flexibility". Change happens, we're evolving as a community to embrace that. Coding (up front) to anticipate change later, is a bad move, which while not the point of the article, is how I read the title and many of the headlines therein.