Be a "qualified" programmer

In fact, this article very early wanted to write, has been busy no time, today finally hollow, the following for the programmer of this profession to say some of my personal thoughts:

To be a programmer in what I think is "qualified," you should do the following:

• Code specification, clear annotation

To be a good programmer, the quality of the code is the most important, the code is the most important resource in the project process, many programmers think it is too cumbersome to write comments, but also spend too much time, especially a lot of smaller companies, less attention to this point, but often to the end of the project, and even after the project was taken over by others, Maintenance costs can become very high, code reading difficulties, comments are not detailed or even not, maintenance personnel need to rely on their own to guess the specific function of a method.

What I'm saying here is that when you get used to writing notes and getting used to the standard naming conventions, you'll find that later maintenance costs are greatly degraded, and that writing a method will be handy when writing the annotations clearly, which doesn't take much time. Many big companies or companies that are more efficient are looking at the code quality of a programmer, so it's important to develop a good programming habit.

• Don't be afraid of trouble, laziness is a big taboo

In my contact with many programmers, I found that lazy more, some people may not understand what I mean by lazy, to give the simplest example, as a return to the previous page of the function, some programmers to lazy directly use Go (-1), but it is not known that this usage often leads to jump errors, Looks like an obscure little problem, but it often affects the quality of the whole system. In order to accomplish the task as the goal, but not to pay attention to the rigor of implementation and the rationality of implementation, Jerry-building, such programmers I believe that no project manager will like.

• Code logic should be rigorous, not only by subjective judgment

Here I would like to give an example, many people will use Ajax to do get or post requests, set the return type is the JSON type, then in the process of the JSON data to think of the first step should be what, according to my coding habits, I will first to determine whether the JSON object is empty, Then in order to determine whether the key value to be read exists, only in the case of the existence of the call, similarly in the background Java code, each object before being called I will add the object is empty judgment, I think with this habit, there will be few empty pointer exceptions. Some people will say I know that the object is definitely not empty, here I want to say is the software this thing has many is unpredictable, since can be rigorous, can be possible to avoid the situation, it is better!

• Be a programmer with a "mind"

It says so much is related to coding, then the last thing I want to say, or feel the most important thing is that we can not do a code-only "robot", a lot of programmers just follow the project manager given the design of the code to do, even if the design is flawed, Or is not reasonable, when the project manager response to a defect needs to be changed, then you have developed before you have to rework, what the programmer is most afraid of, I think we all know, that is constantly changing requirements, change the design, and lead to do no work, write useless code.

In the course of my development in the previous years, I will think of every function, such a design is not reasonable, such logic is right, if not, then I should be how to design, and then feedback my ideas to the project manager or project director, we have discussed after the reasonable plan to enter the development, This can greatly reduce the probability of rework. This time someone will say, our Project manager or project director, Product director never listen to our programmer's idea, then I can only say sorry, you followed the wrong person.

I've been instilling in our programmers the idea that project managers are people, and sometimes we don't always think about the most comprehensive, that they can come up with ideas at any time during their development, and that we can brainstorm about each proposal to determine the optimal solution, which improves the programmer's ability There are great benefits to the quality of the project.

Well, this is the first to write today, the above is only the individual engaged in the development and project management of more than seven years of personal experience, take out to share the next, welcome everyone to correct!



Be a "qualified" programmer