> Design patterns were meant to future proof code Not exactly, most of them are intended to encapsulate change. If you don't have a reasonable idea how your sy

> Design patterns were meant to future proof code Not exactly, most of them are intended to encapsulate change. If you don't have a reasonable idea how your system is likely to change then they're mostly useless. > You probably can't predict the future as well as you think you can It's not at all unusual for people to be good at predicting where change will occur, even if they don't know exactly what the change is. In my field, I have a very good understanding as to where the industry is heading and I design accordingly. > Your program is a document. You can change it. You can make it do anything. Sure, if you're talking about a project with a couple of man years work in it. That's not really the space that design patterns were intended for.