Implicit coupling will stab you in the back!
There are many ways to create implicit coupling in your game project, including the codebase. For example, if you copy-paste some logic in your code, that's an implicit coupling. The easiest way to spot this kind of coupling in your project is to ask yourself this question: "If I change this, do I also need to remember to change something else somewhere else?". If your answer is yes, then there is an implicit coupling between these different parts. The danger with implicit coupling is that it's not tracked by any system, such as a compiler; thus, we rely on the developer's memory or attention to maintain this relationship. The last thing we want to do in game development is to take away the developers' attention or fill their memories with unnecessary information. This reduces their productivity. Also, relying on the developers' memory or attention is not a reliable approach for game development. Humans often make errors, and this is the root of many nasty