Can I learn anything from PHP secondary development?

If you can’t or don’t want to change the position, of course you will say: There is no wrong position, only the wrong direction!

It still depends on yourself ( Recommended study: PHP video tutorial)

Some people draw inferences about the same thing. After solving a problem, they still think about how to prevent it. Is there an alternative or a better solution? Can repetitive tasks be automated?

Someone is insensitive, searching for code, pasting code, shotgun programming. Repeated work is done repeatedly, repeated problems are repeated

Demand becomes faster, and some people think about how to support different demand changes as quickly as possible, how to separate business logic, configure, modularize, and orthogonalize. We also try to strengthen communication in advance, understand user needs, and put forward our own opinions to reduce later demand changes

Some people complain that customers are annoying, product managers are annoying, the code is messed up and patched together, and changes are made again when the needs change. rub. Failure to communicate requirements properly, and confrontation with product managers and customers, asking them to sign "the requirements will never be changed again", or once they are changed, "80% of the system needs to be rewritten, and the time will be doubled"

and Like the original poster, sometimes you can learn a lot, but when you reach a certain stage, there is nothing left to learn. Secondary development can help you understand other people’s design ideas, which is very useful. Just like the previous secondary development of phpcms, it allowed you to I have a deep understanding of MVC, URL routing, and other things. Although I have learned frameworks before, I don’t quite understand the various advanced terms in the framework. Now it’s much easier to look at the framework.

feeling Just do what you want and be done with it. For secondary development, you can take a look at the source code of the developed project.

When you encounter problems, thoroughly understand the principles and get more exposed to other technologies

At the same time, be prepared not to do secondary development, learn more about other frameworks, and write about business

The benefit of secondary development may be knowing which wheels don’t need to be remade!

Secondary development depends on how you do it. I have been doing secondary development of nopcommerce before and I don’t feel that my technology is deteriorating. On the contrary, I feel that it is becoming more and more interesting.

It mainly depends on what it is made of, how many people use it, and to what extent it is developed. The purpose of secondary development is to go online quickly. The work after going online is the most important.

The above is the detailed content of Can I learn anything from PHP secondary development?. For more information, please follow other related articles on the PHP Chinese website!