6 good habits programmers must have to become a better self

If you have the opportunity to get in touch with some technical gurus, you will find that others are not only much better technically than the average person, but also have many different habits in doing things. Habits that are still maintained after so many years in the workplace are often worthwhile. We learn from and learn from.

Today, Uncle Long will share with you some good habits of excellent programmers. If you develop these 6 habits, you can also become an experienced programming driver.

insert image description here


First, code self-testing and re-delivery

Don't rush to deliver the code after writing the code, test the code yourself first, pass the test yourself, and reduce the number of bugs in the code that others find yourself writing, establish a reliable image in front of others, and only gain more trust if the technology is reliable. more likely to be reused.

insert image description here


Second, write readable code

Some people think that writing some incredible, complex code can provide them with job security, because then only one person in the company understands this aspect well, and it is difficult for other people to dye their hands, in fact, it does give you a sense of security It is true that the company cannot lack you, but in fact it has locked itself in, making it difficult to be promoted, because it cannot lack you, so you have been doing this in this position.

Like a pool of stagnant water, the waves are calm.

insert image description here


Third, learn version control tools

Version control tools are a good thing, such as git, which is very powerful. It can not only help us better manage code, but also provide convenience for multi-person collaborative programming, especially in the case of merging code, upgrading versions, etc. to avoid problems. Many unnecessary bugs.

insert image description here


Fourth, technology starts from the foot

Novices always have a good drive and sense of urgency. It is not wrong to want to learn more to improve themselves, but many novice programmers come up with "low-level knowledge" such as Linux kernel source code and algorithm introduction. This is actually Not quite right.

Learning technology is mainly based on what is currently used. Use the learned technology to think about the current work content, and even try to apply it in the work. First, it can increase your sense of achievement, and second, you can apply what you have learned. For example, you can do Even the back-end framework has not been figured out yet, so it doesn't make much sense to study distribution.

insert image description here


Fifth, don’t be too optimistic about evaluating projects

Being overly optimistic means setting a very tight schedule. For example, a project that can be completed in two weeks should leave more time in the project evaluation. This includes factors such as changes in requirements and team changes, and even requires you to move old. code to avoid the embarrassing situation where the time is up but the project is not finished.

insert image description here

Fans who buy for free, move to the CSDN community


Sixth, communication and sharing are the right way

Don't work behind closed doors by yourself, go to technical forums/technical groups to communicate with others when you have time, sometimes you can't understand the problem, others can wake you up with a few words; you can also write your own blog to record your own On the road of technology, while sharing, you will also gain feedback and recognition from others, and even increase your own influence. Isn’t this much more interesting than your current circle?

insert image description here
Today's sharing is here, I hope it can be helpful to you.

insert image description here

Guess you like

Origin blog.csdn.net/zhiguigu/article/details/121712777