This. A million times this.
IMO, the single most important principle is still "Keep It simple when you can, make it complex when you have to."
A system that is simple can be grokked quickly, meaning it can be debugged quickly, modified quickly, new developers can be onboarded quickly,...
Yes complex systems have to exist. Some tasks are complex, and require complex solutions. BUT: Complexity should come into play when it is necessary.
It is perfectly okay to design simple solutions for simple tasks. Yes, sometimes this means ignoring things like DRY.
This. A million times this.
IMO, the single most important principle is still "Keep It simple when you can, make it complex when you have to."
A system that is simple can be grokked quickly, meaning it can be debugged quickly, modified quickly, new developers can be onboarded quickly,...
Yes complex systems have to exist. Some tasks are complex, and require complex solutions. BUT: Complexity should come into play when it is necessary.
It is perfectly okay to design simple solutions for simple tasks. Yes, sometimes this means ignoring things like DRY.