Applying Programming Patterns

Programming patterns (also known as design patterns) are recurring solutions to common design problems in software. Think of patterns such as Observer (for handling events), State (to modularize states and behavior), Singleton (for unique manager objects), Factory (for creating objects), and so on. In game development, specific patterns are also common, such as the Game Loop for the main program of every game (continuous update-render cycle), or a Component pattern for flexible game objects.

By using known patterns, you benefit from proven best practices: it provides structure and readability, and other developers immediately recognize the intention of the code. Such a pattern offers a template solution so you don't have to reinvent the wheel each time.

Starting Points

• Game Programming Patterns
• Design Patterns (Refactoring Guru)

Key Points

• It is important to apply patterns consciously and appropriately – choose a pattern because it helps solve a design problem, not just for the sake of using a pattern.
• You identify design problems in the game and name which pattern(s) are suitable for them.
• You explain why the chosen pattern is the best choice for this case and what advantages it offers.
• You implement the design pattern correctly.
• You present the use of the pattern in documentation or diagram form.