Shulou(Shulou.com)06/02 Report--

This article mainly explains "how to be a better web programmer". The content of the article is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to become a better web programmer".

1. Remind yourself of the need to learn

The step in learning is to realize that you don't understand. Because I don't understand, I need to learn. This sounds obvious, but experienced programmers must remember how long it took them to do this psychological construction. Too many computer science students graduate with arrogance: "I know the most", thinking that they know everything and have a strong desire to prove it to every new colleague. In other words: "I know, I know, I know!" Your attitude will stand in the way of learning new things.

two。 Don't try to prove yourself right.

To achieve greatness-- not just excellence-- you must learn from experience. But be careful, experience will make us repeat the wrong behavior and form bad habits. We've all met programmers with eight years of experience. Keep saying that you are experienced and rely on the old to sell the old. To avoid blindness, you should look back on what you have done and ask yourself, "how can I do better?"

Novice software developers (and many experienced developers) watch their own code in order to appreciate it. They write tests to prove that their code works, not to make it fail. Really great programmers will actively look for their mistakes-because they know that end users will find flaws they have left out.

3. "Code works" is not a sign that you stop; it's where you start.

Yes, the step is to write high-quality software that meets the specifications. The average programmer tends to give up here and skip to the next thing.

But to stop as "finished" is as absurd as taking a picture and hoping it will become a work of art. Great programmers know that * iterations are just * iterations. You can work-so congratulations! But this is not the end. You also need to make the code better.

Some processes define what is "better". Is there any value to make it faster? The document is simpler? More reusable? More reliable? The answers to these questions vary from application to application, but the process remains the same.

4. Write three times

Good programmers write working software. And the software written by great programmers works extremely well. This can rarely be achieved overnight. The software of * * is usually written three times:

First of all, you write the software to prove to yourself (or the customer) that the solution is possible. Other people may not realize that this is just a proving concept, but you know.

Second, make it work.

Third, make it work correctly.

This level of work may not be obvious if you look at the work of those developers. Everything they do seems so brilliant, but what you don't see is that even star developers may have thrown away * and second versions of their software before showing it to others. Abandoning the code and starting over is a good way to incorporate "strive for *" into your personal workflow.

If nothing happens, "write three times" will tell you a lot of ways to solve the problem. It can prevent you from getting into trouble.

5. Read the code, read a lot of code.

You may have heard this advice, but it is actually the most common and valuable advice to improve your programming skills. But many people don't know why it's so important to read other people's code.

When you read other people's code, you have to see how other people solve problems. But don't look at it as literature; think of it as a lesson, a challenge. In order to get better, you have to ask yourself:

How would I write a code block like that? After you see another solution, what do you do differently?

What have I learned? How do I apply that technology to the code I wrote before? ("I never thought of using recursive descent there." ).

How can I improve this code? If it's an open source project and you believe you have a better solution, do it!

Write code in the author's style. Practicing this will help you understand the thinking of the person who wrote the software.

Don't just think about it without doing it. Write down your answers, whether in personal diaries, blogs, code reviews, or on developer community forums. Just as explaining a problem to a friend can help you sort out the solution, writing down and sharing your analysis can also help you understand why you react to other people's code in such a given way. This is the introspection I mentioned earlier, which can help you calmly judge your strengths and weaknesses.

Warning: it's easy to read a lot of code, but it's whimsical to be a great programmer. Many developers "look for answers" through open source code or other software, while most do so by copying and pasting code that happens to solve similar problems. This actually makes you a worse programmer, because you just blindly accept the wisdom of others without digesting and absorbing it.

6. Write code, not just as an assigned task

Working on personal programming projects has many advantages. First of all, it provides a way to learn tools and techniques that you can't learn in your current job, but it can make you more competitive when looking for your next job. Whether you are working on open source projects or providing unpaid work for local community organizations, you can increase your technical skills and self-confidence.

Another advantage of writing code for fun is that it forces you to figure these things out on your own. You can't leave the hard part to others, so it can prevent you from asking for help too quickly.

Tip: don't choose personal projects that you will never fail. You need to fail! But you don't want to fail at work, or when the project has a time limit.

7. Work with other developers one-on-one as much as possible

This helps to listen carefully to other people's thoughts and thoughts. The method can be pair programming, participating in a programming marathon, or joining a programming user group. When you work on an open source project, pay attention to the feedback you get from users and other developers. Do they have anything in common in their criticisms and suggestions?

You may be lucky to find a personal mentor you can trust who will guide you in everything from coding skills to career decisions. Don't waste these opportunities.

8. Learn skills, not tools

Programming languages, tools, and methods vary. That's why we need to accumulate as much experience as possible and use as many languages and frameworks as possible. Focus on the basics of programming, because the basics will never change: focus more on structure than programming. If you think there's only one right way to do things, then maybe it's time for a field test. Dogma will hinder your ability to learn new things and try to adapt yourself to change.

There are many more, but a key principle of self-improvement is to know when to stop.

Thank you for your reading, the above is the content of "how to be a better web programmer". After the study of this article, I believe you have a deeper understanding of how to become a better web programmer. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.