You're generally referring to adding repeated code and yes, this a good thing, normally. However, there is an issue with the attitude around this. Every situation mandates this kind of code structure. This is especially true of bigger games made by older developers. We should avoid adding certain QOL features simply because in a "improperly" coded game it isn't necessary.
Person 1: Y'all need to stop with this softcoding stuff.
Person 2: On the contrary, I believe that "softcoding" can be an extremely beneficial practice for game development. The idea behind softcoding is to make code more modular, reusable, and efficient, which can save time and resources in the long run. First, it is important to understand that there are different types of game projects, and each one has its own set of requirements and constraints. For larger and more complex games, "softcoding" can be especially useful in terms of organization and maintainability. It allows for better code structure and enables developers to work more efficiently, which is crucial for big projects.
Person 2: On the contrary, I believe that "softcoding" can be an extremely beneficial practice for game development. The idea behind softcoding is to make code more modular, reusable, and efficient, which can save time and resources in the long run. First, it is important to understand that there are different types of game projects, and each one has its own set of requirements and constraints. For larger and more complex games, "softcoding" can be especially useful in terms of organization and maintainability. It allows for better code structure and enables developers to work more efficiently, which is crucial for big projects.
by Sykkinu_ January 21, 2023