You need to beat these 10 people to be a part of the procedural world.

Innovation, the mobile Internet is devouring the world, the developer of this career is more hot than ever, and will only become more and more popular. Many people are aware of this trend and join the ranks of writing programs. But although the program engineer sits on a high salary, this is a strong cloud, challenging environment. Because of this, the pros and cons of the quality of developers are always on the network to trigger a lively discussion. Once in the Programmer Inn www.proginn.com Technology Circle There is such a hot question "What is the characteristics of bad software engineers", Amazon software Development engineer Nachiket Naik answer is quite pertinent, get thousands of netizens agree. On the road to top developers, you should avoid becoming the following 10 types of people.

　　1. Copy and paste the person

Program design question and answer website Stack overflow has a very rich resources, many people write a program hit the wall will go up to find answers, Stack overflow itself is not wrong, it is an engineer's right-hand assistant. But if just copy and paste, change a parameter, do not understand the cause and the cause, do not understand why this solution is really applicable to the problems now facing, it is difficult to progress. Many engineers prefer to believe what they see in the online forum rather than bother to test the code or system in front of them.

　　2. People who are too lazy to test

"I don't do tests like that, it's the responsibility of the test engineer. "Even in an era where agile development approaches are so prevalent, this attitude continues to emerge." The inertia of engineers unwilling to test is still common. It may be that they hate setting up a test environment or a lack of consistency in testing. Of course, it's also possible that test engineers have a stigma that can't be said in the developer community.

　　3. Do not write the file person

Some people think that the program Files (code documentation) should be as simple and beautiful as poetry, they do not have the ability to do so, simply do not. But I think this mentality is the number one public enemy of software development. Outstanding software, do not need to have millions of cool features, outstanding software, should be to provide a few people "inseparable from" the continuous use of features, and these several features behind the thousands of people read, update, fix. Developers who despise technical communication, document accuracy, and neglect of details are certainly the biggest stumbling blocks to the company's success.

　　4. The very ugly person who wrote the code

My program can run, but??

Some variables are named x, Flag, str, arr??

Most of the what I write are in one giant method.

Lack of coherent procedural practices or styles

Spraying the global variables everywhere.

For the author, this is the most annoying thing. Although a piece of code is not bad, it may even be the best-written part. Just, if this happens, like a diamond necklace buried in the wreckage of the Titanic, no one can find it, and no one wants to clean it, wear it, use it.

　　5. People with no explosive power

He wrote the program, he deployed, he went on, he did not want to learn to solve the problem, as long as the guy a code, he will fight day and night, and the next day to produce results, you will get a repair, can execute the software, in addition to nothing. Sometimes, when choosing a developer you have to be selfish and find someone who will not only finish the task before the deadline but also have a strong thirst for knowledge.

　　6. Complaining about people all the while

"This is not what I do", "This is not my fault", "This is not part of my repair, it must be someone else screwed up", "this thing is really annoying!" (Infinite Loop) "," I do not know how to fix this side, find a meeting of the people come??

The man who made the mistake may have fixed the move, and you are complaining about it. Complaining does not solve the problem.

　　7. Non-gregarious stubborn people

"Don't do as I do," is the motto of this group of people. In their minds, this is a competition between his "ideas" and your "ideas", his solution and your solution, not the whole project. They will come and go back and forth carefully your implanted code, even if they are functioning properly, tested, and seemingly flawless, still making them feel thorn. This kind of guy is a big trouble to hinder productivity, and when the pressure strikes, they will be the first to flee, even if the experience is rich, the technology is more powerful, and do not easily try to find these people to join the team.

　　8. A timid person

A developer writing Java was stunned to hear that he had to write a python. b The developer panicked as soon as he heard that a part of the profile had to be corrected. C Developers cringe when they hear he has to enter something in the database. These people tend to replicate, unwilling to leave the comfort circle. They have very strange superstitions and do not want to touch certain parts of the system. This is especially true for novice developers, who are fast or slow, eager to jump out of the comfort circle and explore unfamiliar things.

　　9. Vaguely Careless people

Forget about retained backups, snapshot disks, a bunch of archived program catalogs?? These are easy-to-go situations, and as you move towards the professional, these casual situations should be avoided.

　　10. Cleverness scare People

These people can play tricks, "cheat" system to make it work, complacent. The face of complex problems, they seem to change a magic can be solved, but on the author's experience, 10 times there are 9 times are only superficial kung fu, in fact, and sooner or later, will be a problem, resulting in more cost to deal with later.

You need to beat these 10 people to be a part of the procedural world.