Judging the Problem: Code Smells and Refactoring

Introduction After learning about Separation of Concerns, how to see a problem, and how to start separating it in the first article , now we move to the next step, learning how to judge the problem. Once we can identify structural problems in code, the next question is not just what the problems are, but which ones need more attention. Which problems should be solved as soon as possible, and which ones are still good enough for the current context? The main difference from the previous article is that the question is no longer just: what concerns exist in this code? but now becomes: where is the code structure starting to become unhealthy? This part is about learning how to look at working code and ask: what kind of structural issue is happening here? how serious is it? what should be refactored first? what is a real problem, and what is only a smaller imperfection? We will learn about code smells that can be identified in code. But you need to remember its not about memorizing famous