Choosing to postpone the effort to enforce DRY and other similar principles is a choice that must be made based on the project goals. And to be clear: you are postponing the effort, not removing it from the project. Writing sloppy code creates technical debt that is eventually paid for in the slowness of future progress and/or the likelihood of bugs showing up as more changes are made.
Yes, timelines are real. It's also true that you can spend too much time chasing perfection with perfection will never be achieved. But the principles in this article are not about perfection, and there needs to be an understanding of how ignoring them will negatively impact a project in the long run.
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.
Choosing to postpone the effort to enforce DRY and other similar principles is a choice that must be made based on the project goals. And to be clear: you are postponing the effort, not removing it from the project. Writing sloppy code creates technical debt that is eventually paid for in the slowness of future progress and/or the likelihood of bugs showing up as more changes are made.
Yes, timelines are real. It's also true that you can spend too much time chasing perfection with perfection will never be achieved. But the principles in this article are not about perfection, and there needs to be an understanding of how ignoring them will negatively impact a project in the long run.