Redoing Vs. Leaving it beJanuary 3rd, 2020
This is the big question. And everybody should give you a different answer because there is only so much you can do and redoing shit doesn't move your forward. Unless it does.
The answer can often depend on how short-sighted you want to be.
There is always an option to leave things alone, preferably stable and focus on the next better version.
But a better version will surely redo some things. Minimising these things to maximise forward progress.
The best case is to doing it right in the first place. Which can be improbable unless you read about every rookie mistake you are about to make. Alternatively, you learn from *rookie mistakes.* and build perfect the second time. As perfect as possible.
The more perfect things you have in place, the more reliability you can build upon.
Software Developer always striving to be better. Learn from others' mistakes, learn by doing, fail fast, maximize productivity, and really think hard about good defaults. Computer developers have the power to add an entire infinite dimension with a single Int (or maybe BigInt). The least we can do with that power is be creative.