re: The Three Stages of a Developer VIEW POST

re: Accept that low redundancy (DRY) leads to high coupling and balance the two It's hard to convince even experienced engineers of this. Recognize...

Yes. I also know experiences developers that occasionally want to introduce a new common library. And might even be OK in some cases but most of the time the coupling issues weight much higher in the mid-term than the DRY benefits.

Regarding the Code Smells: I would recommend you to read „Clean Code“ by Robert C Martin. If you have a system like sonarqube for metrics, it will show you smells and recommend a fix. Pretty neat.

code of conduct - report abuse