I often see new or simply inexperienced game programmers trying to brute patterns into their code without a single clue as to why they need to think in terms of patterns first, or whether they will benefit from that approach at all. Often times, the programmer has some grand design in mind (getting ahead of themselves, real fast) that the pattern will solve (never finishes enough of the project to get to it), yet does not realize how little of the problem they understand, and even less idea of why that approach is suitable at all.