Experienced programmers trend towards more and more abstraction, resulting in DRY-er code (usually).
Eventually one reaches a point when they realize where duplication makes sense, taking you back to writing code that's superficially similar to what a beginner might do, but with a better understanding of what trade-offs you make.
Trying to predict optimization at the start can lead to yak shaving. Get it working first, refactor later.
Totally. Another popular acronym is YAGNI: You ain't gonna need it. It helps me to think to about that as a counterpoint to other good programming principles.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Experienced programmers trend towards more and more abstraction, resulting in DRY-er code (usually).
Eventually one reaches a point when they realize where duplication makes sense, taking you back to writing code that's superficially similar to what a beginner might do, but with a better understanding of what trade-offs you make.
Totally. Another popular acronym is YAGNI: You ain't gonna need it. It helps me to think to about that as a counterpoint to other good programming principles.