1, should I look at the traditional code or should I look at the MVC framework code?
2, should read the manual or should see the finished item?
My situation:
Learn the basic syntax of PHP, study Typecho topics, and learn about MVC architecture.
I hope you can have a great God to help you tailor a route.
Reply content:
1, should I look at the traditional code or should I look at the MVC framework code?
2, should read the manual or should see the finished item?
My situation:
Learn the basic syntax of PHP, study Typecho topics, and learn about MVC architecture.
I hope you can have a great God to help you tailor a route.
- No matter what style to look at, and do not stay in the eye, hands hack try to imitate/modify some functions. It is not easy to use/design the architecture without knowing what the non-architecture code is like
- When you learn English (the man comes to the English analogy), do you read the dictionary first or read the text first? No matter what, I don't think it's possible. I read a large text without looking up the dictionary, or I read the Oxford dictionary but did not read a half article . It looks as if the latter is reasonable, and the same is true of programming.
to the dictionary (document), you can first according to the degree of commonly used 3,000 words to double-click (there is no experience you do not know what is commonly used problems), but mainly by looking at the side of the finished project side of the document, it is best to ask the project author, a general explanation. (equivalent to reading the text while looking at the dictionary, and then at the same time the teacher explained) open-source projects, can not find the author could find a variety of blog posts
Skill tree In fact, no matter what language should be the same:
LV0 can only grammar
LV1 understand how to work, can check the bug (not too complicated)
LV2 has some ideas to add simple functions
LV3 can identify problems, optimize local structure/performance, and solve complex problems
LV4A to the architecture, grasp the macro-structure, grasp the technical system of the whole project
LV4B to command has experience, can command LV2 LV3, reasonable allocation of tasks, avoid technical risks
LV4C resources, can from within the company/outside to fight for LV2 LV3 people need of all kinds of resources
Lv4d to diplomacy, to work with people from other departments.
LV4E has experience in teaching, can guide all kinds of people upgrade dot
LV5 Master A number of LV4 skills, and know how to recruit and straighten out other LV4
Look out, I just want to lv4e the proficiency of this skill haha
Let's write something first.
Personal humble opinion, the domestic do PHP revenue is to do the bottom performance optimization, the vast majority of PHP developers no matter how many frameworks he knows, proficient in various mv* design days are very general, or you struggle for a product out of the investment is more promising.