I don’t know what your development method is like.
It is an ideal situation to think clearly about this from the beginning, and there are not many times like this.
It is best to spend part of each sprint (or development cycle) optimizing the structure. Don't wait! Once you wait a little longer, basically the architecture will have to be replaced or used as a makeshift.
Also, it is unlikely to spend a lot of events on optimizing the code architecture. After all, the business line will not give that much time.
Is it true to say "premature optimization is the root of all evil" and why?
Maybe you can refer to this question
It’s never too early to optimize your code structure
I don’t know what your development method is like.
It is an ideal situation to think clearly about this from the beginning, and there are not many times like this.
It is best to spend part of each sprint (or development cycle) optimizing the structure. Don't wait! Once you wait a little longer, basically the architecture will have to be replaced or used as a makeshift.
Also, it is unlikely to spend a lot of events on optimizing the code architecture. After all, the business line will not give that much time.
Work -> Right -> Fast
is not a reason to write bad code