There are too many security and design flaws. How do programmers face the temptation to reconstruct the entire project?

I have been in the IT industry for 7 months, and I am a programmer who has just wet my shoes

Under development, need to learn various knowledge

There are html css javascript vuejs various web front-end frameworks regular expressions php and thinkphp frameworks
and databases

There are too many aspects involved and I haven’t learned much in the past six months. I have to use what I need to read, so I will encounter many problems.

When making bs software, I often find some problems. After solving the problem, I will find that the code I wrote before has left bugs and design flaws that I never thought of before.

At this time, I had an idea to get rid of all the previous bugs. The problem came. Some problems were not considered carefully at the beginning, so I just wrote the code directly. If you want to correct it, many places will be affected. You may get dizzy, and if you don't pay attention, you will go back to the previous strange circle.

At this time, I wanted to refactor the entire project code, but another problem arose. The development time required by the product manager was not enough (the function he wanted was expected to be developed in one day, but it actually took me 3 days) , when refactoring code time is more valuable than gold. And the product manager will say every day that it is too slow and needs to be accelerated (the product manager is the company CEO and also my teacher).

Every time this happens, I feel very impetuous and can’t write code with peace of mind. I always think about the bugs in the project.

Let me ask some experts who have the same sentiment as me how to solve this problem.

It is to continue development. After the first version of the product is developed, it is better to develop the second version.

It’s better to refactor directly. I want to refactor directly. Personally, I think if a program needs to be refactored during development, regardless of whether the product functions have been fully realized, it can be regarded as a version, so that the new version can be It will be safer.

After writing this, I already have the answers in my mind and have clarified a lot of things.

I went to back up the code. Teachers are welcome to provide more experience.

This question has been closed due to non-technical discussion

Reply content:

I have been in the IT industry for 7 months, and I am a programmer who has just wet my shoes

Under development, need to learn various knowledge

There are html css javascript vuejs various web front-end frameworks regular expressions php and thinkphp frameworks
and databases

There are too many aspects involved and I haven’t learned much in the past six months. I have to use what I need to read, so I will encounter many problems.

When making bs software, I often find some problems. After solving the problem, I will find that the code I wrote before has left bugs and design flaws that I never thought of before.

At this time, I had an idea to get rid of all the previous bugs. The problem came. Some problems were not considered carefully at the beginning, so I just wrote the code directly. If you want to correct it, many places will be affected. You may get dizzy, and if you don't pay attention, you will go back to the previous strange circle.

At this time, I wanted to refactor the entire project code, but another problem arose. The development time required by the product manager was not enough (the function he wanted was expected to be developed in one day, but it actually took me 3 days) , when refactoring code time is more valuable than gold. And the product manager will say every day that it is too slow and needs to be accelerated (the product manager is the company CEO and also my teacher).

Every time this happens, I feel very impetuous and can’t write code with peace of mind. I always think about the bugs in the project.

Let me ask some experts who have the same sentiment as me how to solve this problem.

It is to continue development. After the first version of the product is developed, it is better to develop the second version.

It’s better to refactor directly. I want to refactor directly. Personally, I think if a program needs to be refactored during development, regardless of whether the product functions have been fully realized, it can be regarded as a version, so that the new version can be It will be safer.

After writing this, I already have the answers in my mind and have clarified a lot of things.

I went to back up the code. Teachers are welcome to provide more experience.

If you don’t have time and perseverance, of course you should develop new features first. Isn’t it true that all new software in the world is full of bugs? After it goes online, after you fix the bugs, your market and reputation will be overtaken by others. Besides, after you continue to think about new features, you will be able to see its overall structure and shortcomings more deeply. At this time, even if you modify bugs and start over, you will be able to complete it in one go without any sense of stagnation.

The simplest point is that even if you overturn it now and start over again, more than half a year later, when you look back at the program you rewrote, you still have the urge to overturn it

I don’t understand why you changed the title and asked the same question again.
Refactoring the code can eliminate bugs caused by your previous wrong thinking and patterns, but you must know that this may take a lot of time, and the BOSS may not be satisfied.
It is recommended that you take some time every day to catch up on computer English, and then learn the mature PHP framework, so as to improve development efficiency and reduce the probability of BUG occurrences as much as possible.

We can give priority to version v0.0.0.1, solve bugs immediately, update functions iteratively, and solve bugs while developing new functions.
As mentioned above, after more than half a year, when you look back at the program you rewrote, you feel the urge to overturn it.
Our technology is constantly updated, and so are our skills
When you are exposed to more technologies, you may feel lost in reality at first
When you calm down, you will find that only the original The version does not affect the user's use, and you can get through it in your heart.
The only martial arts in the world is fast and unbreakable

I have encountered this kind of problem before. Solve the problem first and reconstruct it when you have time. I am also in the process of refactoring now, 70%. . .