I always want to refactor the entire project.

I entered it7 months as a developer who just got wet shoes. I need to learn a variety of knowledge, including htmlcssjavascriptvuejs, various web front-end frameworks, regular expressions, php, thinkphp frameworks, and too many database-related aspects. I haven't learned much in six months, what to use... I joined it7 months as a programmer who just got wet shoes.

Various knowledge needs to be learned during development

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

There are too many things involved, and I have not learned much in the past six months. so I have encountered many problems.

Bs software often finds some problems. after solving the problems, it will find that all the previously written code has left behind bugs that I did not think of before.

At this time, there is an idea to eliminate all the previous bugs. at this time, the problem arises because the code was directly written without careful consideration. If you want to correct it, it will be affected in many places. It may get dizzy, and if you don't pay attention to it, it will go back to the previous strange circles.

At this time, the code of the entire project needs to be reconstructed, and another problem arises. The development time required by the product manager is not enough (the functions required by the product manager are expected to be developed in one day, but in fact I spent three days), refactoring code time is more valuable than gold. And the product manager will say it is too slow to accelerate every day (the product manager is the ceo of the company and also my teacher ).

Every time, I was so impetuous that I could not write code with peace of mind. I always thought about bugs in the project.

Ask me how I can solve this problem.

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

I personally want to directly refactor the program to make it safer.

This issue has been closed. cause: non-technical questions are discussed.

Reply content:

I joined it7 months as a programmer who just got wet shoes.

Various knowledge needs to be learned during development

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

There are too many things involved, and I have not learned much in the past six months. so I have encountered many problems.

Bs software often finds some problems. after solving the problems, it will find that all the previously written code has left behind bugs that I did not think of before.

At this time, there is an idea to eliminate all the previous bugs. at this time, the problem arises because the code was directly written without careful consideration. If you want to correct it, it will be affected in many places. It may get dizzy, and if you don't pay attention to it, it will go back to the previous strange circles.

At this time, the code of the entire project needs to be reconstructed, and another problem arises. The development time required by the product manager is not enough (the functions required by the product manager are expected to be developed in one day, but in fact I spent three days), refactoring code time is more valuable than gold. And the product manager will say it is too slow to accelerate every day (the product manager is the ceo of the company and also my teacher ).

Every time, I was so impetuous that I could not write code with peace of mind. I always thought about bugs in the project.

Ask me how I can solve this problem.

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

I personally want to directly refactor the program to make it safer.

You choose a mature PHP framework, suchYII2,LaravelAnd so on.
If you are always confused, it will only waste time.Otherwise, you will always feel this way.:

My personal suggestion is to write code with a focus on modularity and governance. you may wish to consciously try unit tests in the next project. when writing code, try to think about which content may change and will not change, do you need to consider encapsulation and the overall framework. I used a project to complete a mobile ui component library. although many bugs were not maintained, when I wrote a mobile terminal, I used others' frameworks, I also think it was quite smooth, because I had thought about it myself, and naturally understood the pain points they had to solve for framework developers, and understood some of their ideas. it was good for your code integrity.

The code will never be perfect. It is just constantly becoming perfect. we can see that the previous shortcomings are very good, indicating that the progress has been improved.

In this case, it is not just for newcomers. if the project is large enough and the cycle is long enough, the previous model is not suitable as the business volume and business complexity increase.
Unless you anticipate this at the beginning, and then select the appropriate mode or framework.

However, in this case, we have to "gradually rebuild" it's time to modify and refactor some of the code related to the new features, after a version iteration is complete, you need to complete the reconstruction.

The above is for reference only.