You can’t be serious about this. Design patterns and CC often DO complicate things, not just in game dev, but in all software development. The reason is simple. You're telling people to follow solutions that might have worked in another scenario and use them as the foundation for their own code organization. That’s INSANE! The result is complex and slow software. Different problems require different solutions. Yes, there’s overlap, but being dogmatic about it, like telling people how long a function should be, is just harmful. A better approach is to solve the problem in the simplest way. As the codebase grows, you identify common patterns and introduce necessary abstractions. This works because you're working with the ground truth. You know the code’s strengths and weaknesses, so you can adapt by introducing new concepts. Designing upfront usually fails because there’s only so much you can keep in your head. How many times have I tried to design something upfront, only for the actual code to change so much that the original design falls apart? Upfront design doesn’t work because, most of the time, you’ll be wrong! And design patterns are exactly that, formalized best practices. When people start by writing tons of unnecessary boilerplate to follow these practices, they’re wasting time and making their future work harder, for themselves and the CPU.