When writing code for the new system, I do not want to introduce unnecessary complexity in the design, which I will never need. Therefore, I follow YAGNI here, and, rather, refactoring, as I see the need for more flexibility or how responsibilities become more clear. This allows me to move faster.
But there is a problem with the junior developers, because they will not know when to reorganize or build the project. They simply add more code to the existing design.
So what are the best ways to solve this problem? Should I build a more robust design more often, so when adding to it, they have a good example to follow, even if we may never have to add something? Or should I just continue browsing code, education, etc.? Or both?
Do you have any problems with this type of problem? How did you solve it?
source
share