Preface
When it comes to typing code after watching a video, the biggest taboo is to follow the video exactly from the beginning. Even if you follow the video and complete a project, you will never be able to turn the specific knowledge into your own. Simply It is just a simple reproduction. The author of the video himself will not release the bugs and debugging process he encountered during the project, so what you learn is an almost bug-free project, so you Lacking an active exploration process, a smooth project with no bug debugging will naturally not impress you. This is why you will feel a sense of emptiness after completing the project, although you may not have enough requirements for the project at the beginning. It will be slightly lowered, but you might as well try to thoroughly study a project from the beginning. It can be said that this is the only way to really learn something from doing a project. You can try the following method before doing a project next time. I hope it can be helpful to you. Helped~
1. Understand the project itself
Before choosing this project, you must first ask yourself, what exactly does this project do? What are its usage scenarios? What is its overall business process? What is the concept of Q in its architectural design? What specific technologies does it use? Having a general understanding of the project is very necessary for subsequent in-depth study of the project. At this time, official documents are very important. Take the
projects in github as an example. Generally, there is a document that introduces the project. Some projects will even explain the current situation and related plans for the future. With this, we can grasp the design concept of the project as a whole.
2. Ensure code operability
After determining a project that is suitable for you, you can set up the environment, debug the environment and then further operate the code. The operation mentioned here is not just typing the code according to the video like the questioner did. Most of the teaching videos nowadays are generally Q Related files of the source code will be attached. You can try running these codes on your own computer to ensure that the code of the selected project is executable on your computer. First of all, the size of a project is generally relatively large. If you start typing code without such preparation in advance, it is sometimes difficult to detect errors during the coding process (especially some particularly subtle errors, I know this deeply).
For Java, you need to pay attention to the development environment that is consistent with the requirements of the project and determine the version of jdk. If the jdk version is different, it will cause some problems, such as garbled Chinese characters, prompts for compilation errors, etc. I believe many people are new to this point. We will encounter it every time,
and we are often at a loss when we encounter it. It will take a lot of time and even kill the mood of working on the project, so it is important to ensure the consistency between the development environment and the project in advance.
3. Learning the project process
For the study of the project, it is recommended to start learning from the main process of the project, and then refine the branch processes. What is the main process called? For example, if you are working on a Java project, you start with a new project, encapsulation, global exception handling,
spring integration, solving authentication and authorization issues, cross-domain issues,
and then the development of business functions (menu management Q, AP | interface Development), then to the deployment of the project, and finally publishing it online. This is a rough main process. You must have a deep understanding of the basic technical knowledge used in the main process, including the principles and methods of its implementation. Wait, these should be basic skills. If you are not familiar with any knowledge point in the project process, you should go back and check it out immediately. Don't put yourself in an overly passive position during the project process because of the weak foundation. .
4. Partial or super-categorical practices are often tried only briefly.
What is mentioned above is
the attitude of "breaking the casserole and asking for the bottom line" regarding the basic knowledge of related technologies, but it is not applicable to
all . Some implementation methods of the project may be relatively biased or beyond one's own understanding. For this kind of basic knowledge Q that no longer belongs to the basic category, if you study too deeply, it
will not be beneficial to the progress of the project, and you may also become more confused the more you study, because the knowledge involved in some details is far beyond The scope of my own knowledge is limited. In short, the technical level is not up to the level. It is enough to have a general understanding of these.
5. Summarize knowledge points in a timely manner
. Finally, it is inevitable to summarize the knowledge points in the project
. My suggestion here is to open a computer note-taking application such as
Typora or Microsoft's note-taking software Onenote. These have more to help you manage. The function of notes realizes classified management. If you are doing a project for the first time, there must be a lot of knowledge points that need to be recorded in the project. If these summary knowledge points can be saved, they will definitely become your reference for future projects and even work. Valuable experience, organized and clearly classified notes are necessary for your efficient review in the future.
