[tayip9]

It depends.

If you feel like you're close to product/market fit or if your runway is short on your startup, you might want to continue the way you've been doing things.

On the other hand, as a self-taught programmer, I imagine there are a lot of skills that you can improve on. The danger of writing spaghetti code is you can't reuse it, and if you continue to write spaghetti code, it be becomes a habit. In the long term, your best investment is in yourself. Time spent on getting good at your craft may help you to get your product to market faster.

Also think about how much time you expect to use on revising/debugging old code. If you expect to extend or build on top your code, it is usually worth spending time revising it. I like to believe there are different degrees in quality for code. Spend more time on more vital or core components and less on others.