Ten suggestions for novice programmers

ten suggestions for novice programmers

1. A CS-related degree or a diploma in science and engineering is not necessary for you to become a programmer.

This is a lifelong learning career. Beginners, transcoding and even after a long career will certainly encounter many setbacks and problems, but the factor that determines whether you can get started and go on this road will not be the type and name of the degree you are holding now.

2. Try to be patient and get enough sleep.

Learning and memory usually depend on three steps: acquiring new knowledge, forming and consolidating memory, and recalling information already stored in the brain. Among them, the acquisition and memory of new knowledge can only happen when we are awake, but dry sleep plays a vital role in strengthening the connection strength between synapses of neurons, so the formation and consolidation of memory usually occurs in sleep. If you are exposed to a lot of new knowledge and find it difficult to digest, don't be anxious and depressed. Maybe after a few sleeps, you will find yourself mastering them gradually.

3. master the search ability and skills, and accumulate reliable information sources.

With the development of the information age, the ability of information acquisition and screening must rank among the top skills required by programmers, and even determine your level more or less, especially in this industry that attaches great importance to sharing and collaboration. For novice programmers, the fancy advanced search skills of search engines are inevitably not practical, but even when searching with the most plain keywords, how to use words accurately needs to be worked hard.

4. Search in English flexibly.

Mastering English search will be a universal weapon for programmers to grow up. Regardless of the quality and quantity of English resources, most mainstream computer languages are developed in English, so as long as English keywords are put into google search box, you can get search results in all common languages of your browser, including English. For example, I can usually get matching content in Chinese, Japanese and English. Only using Chinese search will greatly limit the quality and quantity of search results.

5. Knock on the code more often. Imitation is the beginning of learning.

When learning with youtube videos or other tutorials, don't copy and paste them. Try to type out the simple code or the code that is difficult to understand and run it line by line.

6. Don't forget to add your own ideas and creativity to the imitation.

Although you may only be able to follow the tutorial to do some small projects in the early stage of study, thinking about how to expand projects according to your own interests and realize them technically can usually bring valuable growth, and can also enrich your portfolio and show it to your potential employers when you apply for a job.

7. Avoid making wheels repeatedly, but don't blindly copy other people's codes.

It will be a good way to learn from the codes written by people who are better than you, but remember not to blindly copy the codes that you can't understand. Not only won't you learn anything, but it will probably cause a lot of problems that you can't solve.

8. Master a language or framework first, and then dabble extensively.

Although technology is developing with each passing day, it is far from enough to go deep into a language, but only on the premise of mastering a language or framework can we gradually see the similarities, differences, mutual learning or innovations between different language frameworks.

9. Pay attention to the readability of naming.

Don't name class names, variable names or method names that are meaningless or misworded, and don't make spelling mistakes when naming them. If you have no confidence in your English, look it up in the dictionary before you start, otherwise the cost of modification/maintenance and the difficulty for collaborative developers to read your code will increase exponentially.

1. Think clearly about the problem to be solved before writing code.

It will help you get twice the result with half the effort by taking the time to clarify the purpose and implementation method of the code. Writing the code is usually only the last step besides testing, and it is also the simplest step.