What to do if, with the growth of the project, the architecture turned into porridge and redneck code?

Question

Django

Good afternoon! There was a small project, which expanded over time and reached a level where it is already much more difficult to maintain and expand it with the current architecture. At that time, I could not foresee this, the experience was not enough. It takes a long time to rewrite from scratch, and it’s not a fact that the new architecture will not turn into the same mess later on. Can anyone advise smart books / articles on this issue or just help with advice?
The project is written: server side in python (django), client side in javascript (jquery). I am the only one doing programming.

Answer 1

Just keep writing code. Develop.
After all, if you didn’t do this - didn’t write a bunch of redneck code, now you wouldn’t understand that you can do everything better.
There is time - do refactoring. This is extremely interesting.

Answer 2

Maybe it's time to get familiar with refactoring ?

Answer 3

Bydlokod does not mean bad, the main thing is that it works, not to be confused with shitty bydlokod - the
younger generation remembers Word 97.