👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
I don't see that you are advocating for writing bad code anywhere. Everyone here wrote the best code they could at the time. Things change over time and that's ok.
Legacy code that works, but is different, doesn't need rewritten. Unless there is a perf, UI, ux, or new feature leave it. But when time comes to touch that module/function/component make it better.
I wouldn't advocate for shipping bad code because you were to lazy or under a time crunch to refactor as you went. All too often I find folks swimming through an unmaintainable mess for days. 1hr of refactoring makes all the difference in the forward movement of the project.
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.
I am a big fan of the "boy scout rule".
I don't see that you are advocating for writing bad code anywhere. Everyone here wrote the best code they could at the time. Things change over time and that's ok.
Legacy code that works, but is different, doesn't need rewritten. Unless there is a perf, UI, ux, or new feature leave it. But when time comes to touch that module/function/component make it better.
I wouldn't advocate for shipping bad code because you were to lazy or under a time crunch to refactor as you went. All too often I find folks swimming through an unmaintainable mess for days. 1hr of refactoring makes all the difference in the forward movement of the project.