7 bad habits of inefficient programmers

Programmers always want to be as efficient as possible, but many people tend to feel overwhelmed. This is because they have developed some bad habits in the coding process for many years. The following 7 bad habits are absolutely what software engineers need to get rid of.

Seven-bad-habits-of-ineffective-software-engineers

1. Lack of passion

This is already a commonplace topic, but it is the truth. After years of writing code, programmers are likely to lose their passion and just think about clock. What's worse, this sentiment is contagious to the people around them like a plague. "Even if you write a whole day of code, you should be talking about it at lunch and after work," said Liz Eggleston,course report--, co-founder of the online resource for learning to encode. Lack of passion can lead to idleness. Idleness can lead to work errors. Software engineers need to rediscover their passions.

(Code Agricultural Network recommended reading: "Improve programmer productivity 5 Tips")

2. Do not like test code

Software engineers once thought testing the code was none of their business. But this is not the case in reality. If you still think so, then you are either ignorant or arrogant. "The test is not a flower that can be added to the brocade, but the charcoal that must be burnt in the snow," D.J charles,invaluable--, a CTO at an online auction market.

"There's no need to be embarrassed by bugs – good quality assurance works are great security," he advises, "and no one can identify every test case and result." Finding bugs in QA is always better than finding bugs in production.

"Inefficient engineers have no sense of testing," he added, "and often the best performers are those who strongly require testing time and testing automation." This is their lesson. They already know the importance of testing through their own experience. ”

(Code Agricultural Network recommended reading: "What killed the Software Testers?") 》）

3. About usability is completely out of the consideration

Inefficient software engineers believe that their job is to provide applications, rather than letting users who use them to help them do their jobs accept and hold the app. They don't treat users as customers: They think users are the source of trouble. "Sometimes it's hard to get engineers to connect to the real world," invaluable Charles explains, "inefficient engineers will mistakenly characterize user experience issues as other people's problems." ”

Unfortunately, it seems that many software engineers hold this attitude, which is why businesses are looking for code fighters who can empathize and understand the problems of others. "Employers are struggling to find people with the technical skills and knowledge of basic peripheral business issues," said Matt Sigelman,burning, CEO of Glass technologies--, a job market analyst.

"Even good programmers may say they are not interested in understanding the business being solved," he continued. "They'll say, ' Give me a spec. I will write according to the norm. ' It's an inefficient programming. “

4. Like to say "no"

Inefficient programmers lack the "vision" of things. As a result, they often say ' no ' to the project, or become a strong negative force on the way to the project. "When faced with a challenge, a positive attitude makes people dare to face all potential possibilities," Charles explains.

"Saying ' no ' is tantamount to closing the door to creation," he continued. "Whether you think of a good idea or not, you need to keep an open mind to wait for the inspiration to knock on the door. ”

One reason why inefficient software engineers are quick to say "no" is that once they have a job, they don't want to be distracted by other things, for fear of being disrupted. "No one is perfect, and fear of being disrupted is the choice between safety and non-innovation," said Charles. "Engineers need to be free to try new things." Some ideas are initially identified as "crazy", and the end result is an innovative and groundbreaking solution. ”

5. Do not like to study, refuse curiosity

Inefficient software engineers are rejected learners who are reluctant to learn new ideas. This attitude is expensive in all occupations, but it can be a career terminator for software engineers. "You have to have constant learning curiosity because programming is a lifelong learning process," says Eggleston of Course report.

"You need to reach out to other people in the community to keep up with the latest demand technology, because technology is constantly changing. "She suggested that.

Research and development conferences, webinars, and weekly lunches with colleagues are some of the activities of software engineers to avoid inefficient learning, Charles points out.

"Good software engineers have an innate instinct for learning. "He said so.

6. Can't get along with others

Inefficient software engineers cannot be members of a team. This may be a very real problem in today's development world-more and more team work. "The software project is getting more and more complex," said Burningglass's Sigelman, "The days of programming like a lone wolf are gone." ”

Charles points out that while inefficient software engineers cannot be good team members, they still rely on other team members. "Keep in mind that there are always some potential things that you rely on for the code you are writing-and that the code you are writing depends on something that is changing," he said.

He added that complacency would also limit inefficient software engineers to being a competent team member. "It doesn't matter if you get stuck in a problem from time to time. Knowing when and how to climb the track is the key to success. Don't let complacency become a stumbling block for you. ”

Lack of communication skills can also make the software engineer's team setup inefficient. Especially when inefficient engineers communicate with people outside the team. "Developers who lack the ability to communicate with non-technical team members are often less successful," Eggleston noted.

When it comes to intra-team communication, we may be able to put a low-efficiency engineer on the horse, Charles points out.

"Not being able to work with others is more a matter of personality than a conscious decision," he continued, "allowing developers to go into other business circles and learn their communication skills, though not something developers want to do – is a great way to overcome this shortcoming." ”

7. Do not care about security

This is a bad habit that both efficient and inefficient software engineers can develop. In many development product stores, security is often an extension of the finished product, which is not the best way to address security. "Developers need to put security first when coding," says Stephen newman,damballa--, CTO of a cyber threat detection company.

But even software engineers who get a degree in computer science have not been trained in this area. "How to build secure software has not yet become a requirement for most universities," Newman points out.

"We've only dealt with the problems we've discovered before, but now that there are so many attacks in the cyber world, you have to put security first," he adds, "a really good programmer will take security into account in his design and architecture and all the code-related places." ”

Bad habits can make all professional workers inefficient. For software engineers, bad habits, such as being uninterested in a project and refusing to be a team member, can undermine the entire team. Many inefficient software engineers are not at the beginning, and are not going to change. Through regular self-assessment, bad habits can also be identified and eliminated, so inefficient software engineers can also become effective talent. Have you ever met an efficient software engineer? Aren't you one of them?
All-in-one programmer Exchange QQ Group 290551701, gather a lot of Internet elite, technical director, architect, Project Manager! Open source technology research, Welcome to the industry, Daniel and beginners are interested in engaging in IT industry personnel to enter!

7 bad habits of inefficient programmers