>The shape of a program should reflect only the problem it needs to solve. Any other regularity in the code is a sign, to me at least This is just so wrong. Th

>The shape of a program should reflect only the problem it needs to solve. Any other regularity in the code is a sign, to me at least This is just so wrong. The shape of your program should reflect your understanding of the problem, and the clearest way to communicate that to other humans. Patterns will be a part of this, as it reduces the amount of mental effort required to understand the solution. It is true that writing too much boilerplate to create a pattern is a sign that your language is lacking necessary abstractions. But patterns themselves will always be a part of good software. I swear this entire thread is just trying to rationalize bad programming practices.