Dear elders, I am very upset to ask you a question. I am a newbie and don't know how to say many things. let me give you a rough description. I hope you can give me some advice. thank you.
A project consists of a lot of code, but the code is also divided into many files
For example, view. php is used to query a database.
Insert. php
UPDATE Database data update_db.php
......
There are a lot of files and a lot of code. if every piece of code can be understood, but it still feels messy, why? Where did you learn well? It seems like this for a project with a relatively large amount of code in the book. how can I understand other people's projects ??
Reply to discussion (solution)
First, let's take a look at naming. unless you encounter a program with a strange name, you generally know what functions this function or class implements.
Then read the notes. if so, you can further understand the functions of the program block.
First, differentiate what each block is, and then look at the block you want to know.
For example, if you only want to know the logon information of a member system, you should not retrieve the password. The same is true for other people's code.
I recently got more than million files in the system. there are still a lot of files except cached images and directories. The most important part is the half index. It is recommended to take notes while reading. The first time can be very fast. You can understand what this file is.
I recently got more than million files in the system. there are still a lot of files except cached images and directories. The most important part is the half index. It is recommended to take notes while reading. The first time can be very fast. You can understand what this file is.
Can I just understand the general information ??
The basics are very important. read more documents.
I just upgraded from a newbie to a newbie...
I personally think that other people's code mainly depends on the architecture and design mode. Specifically, a function is used to directly ask the search engine for the principle, and then try to implement it by myself.
Starting from the functional module, you need to know where you want to know first. First, you need to know what he wants to do. when you know what he wants to do, do you feel like it can be done, if you can complete OK, check it out first. if you do not understand anything, you must understand it. Otherwise, you do not have the courage to change the code for fear of errors.
The greatest truths are simple. Mentality. Down to Earth. Spring branches. You can see the scenery along the way by train. Fly to enjoy the colors of the cloud
There are a lot of files (you have a lot of treasures), and there are a lot of code (there may be spam code, don't bother), if every piece of code is understandable (if a bit self-deception. It is better to read a piece of code first), but still feel more and more chaotic (with no grain in hand. Panic. Enrich yourself). why? (I believe you will succeed)