Programming cognition: Multi-thinking, multi-coding, and multi-test

Each programmer has his own unique programming method. in his career, BenTeese, the original author, came up with some insights on the coding process: Thinking, coding, and testing. Every Programmer has his own unique programming method. in his career, Ben Teese, the author of the original article, came up with some insights on the coding process: Multi-thinking, multi-coding, and multi-testing. The process of building software is a process of continuous learning. a good strategy is to follow the plan-execution-reflection process.

During my career as a programmer, I realized one of the following program coding procedures. I also came into contact with many other theories and ideas, but I still think this is the most suitable for me.

The general style is as follows:

A: Think a bit)

B: Multi-encoding (Code a bit)

C: Test a bit)

Next (Go to Step 1)

Step 1: think more

How many of my friends think that the speed and speed of the keyboard pattern represents the productivity of the program? If you think so too, I hope you can put it in your mind when you encounter problems.

If you cannot start thinking about it, ask yourself: What exactly do you want to do? Once we have calmed down, the answer to this question will help us identify the direction or rethink the solution.

In the next step, I will suggest you think about this question: do you want to complicate the simple question? Trying to solve the problem in the simplest way is what every programmer should do. However, when we have enough knowledge, is it easy to solve the problem with such a simple method? If we think this way, we may find a bunch of more and more complex problems. Let's take a look. what is the worst result of a simple solution? Is it worse than it cannot solve the problem? It is important to learn to jump out of the corner.

Therefore, when you encounter problems, you may wish to ask yourself more questions. When a bottleneck is reached, I will consider the next step.

Step 2: Do More

How many of my friends think that the speed and speed of the keyboard pattern represents the productivity of the program? If you think so too, I hope you can put it in your mind when you encounter problems.

If you cannot start thinking about it, ask yourself: What exactly do you want to do? Once we have calmed down, the answer to this question will help us identify the direction or rethink the solution.

In the next step, I will suggest you think about this question: do you want to complicate the simple question? Trying to solve the problem in the simplest way is what every programmer should do. However, when we have enough knowledge, is it easy to solve the problem with such a simple method? If we think this way, we may find a bunch of more and more complex problems. Let's take a look. what is the worst result of a simple solution? Is it worse than it cannot solve the problem? It is important to learn to jump out of the corner.

Therefore, when you encounter problems, you may wish to ask yourself more questions. When a bottleneck is reached, I will consider the next step.

Step 3: Multi-test

This step is not just as interesting as coding, but even annoying.

However, if there are no projects in the test phase, I suggest you do it in your personal open-source project. because it is released without testing, not many people are willing to use it.

In addition to worries, testing may be the most complicated part of the coding process. Different from what you see is what you get in programming, finding the best test solution can be multiplied. Testing is characterized by uncertainty.

Some of my friends use a test-driven development method. my opinion is: this is good, but stick to it. For me, I will also use this method for highly algorithm-concentrated projects.

Step 4: try again

The solution to the problem is often not achieved overnight. Loop and feedback are crucial. The process of building software is a process of continuous learning, and continuous learning and strengthening the capabilities of technology and problem handling. A good strategy is to follow the plan-> execution-> reflection process.

Summary

The above are my personal opinions on coding processes. Today, with the introduction of more and more convenient development tools, the above four steps have become smoother. So try it.