Raghuraman thinks software development is an art, not a science

You can learn a variety of techniques for software development, but you still need to be passionate about coding. If you are such a person, then you can become a "great developer." Raghuraman lists the good developers should have attitude:

Attitude 1: Defects indicate a problem with my ability to write good code

Modifying defects is a daily activity of software developers. Obviously, the flaw is the biggest enemy of developers. When modifying defects, how many people can think of the following:

At first, what can I do to avoid this flaw?

How can I let this defect escape my eyes?

Well, since the problem has arisen. How can I avoid the same mistake next time? What to do next?

In fact, few developers think so.

Those who are willing to be good developers should see flaws as a threat to their place, a threat to personal credibility, and a threat to programming skills. It is this attitude that makes it a great developer.

Attitude # 2: Testers, having the ability to spot bugs in my code

How many people have this attitude? Many developers think the task of testing is to find flaws. That's true, but that does not mean that developers can treat defects as something they should. Good developers are willing to invite testers to look for flaws in his code. They have such confidence in their code.

Attitude 3: No compromise on code quality issues

For developers, the most important thing is the quality of the code. This includes the correct coding standards, proper design and refactoring to make the code more maintainable, and more. However, we usually compromise on code quality issues for a number of commonweek reasons, such as the pressure of time and progress. Good developers should never compromise on the quality of the code, no matter what the problems are.

Attitude 4: Confident but not arrogant

Good developers should be confident about their abilities, but should not be arrogant about other developers and testers. He should always remember that he is a part of a team that wants to accomplish the project's common goal on time and with good quality.

Attitude 5: Grateful testers

Although good developer work is very hardworking, testers still may find flaws in his code. If so, thank these great testers. Good developers should thank the testers for the defects they found. He should keep in mind that his enemy is a flaw, not a test person.

In a paper for software testers, Raghuraman believes that developers and testers work in exactly the opposite direction, but share a common goal of producing high-quality software. He believes that the best testers should have the following attitude:

Attitude 1: I want to destroy the software at all costs

Do not create misunderstandings! The testers' job is to find flaws, and in the process, make the software better and better over time. Defects are testers good friends, so his most important thing is to destroy the software at all costs, and found loopholes. In this process, test cases can be executed systematically, and temporary tests or exploratory tests can be conducted.

If you want to be a good testers, then your attitude should be "to destroy the software at any cost and find flaws."

Attitude 2: Excellent developer, I must find the flaw in your code

Do not know how many testers can have such an attitude?

But if you want to be a good testers, you need to have the attitude: no matter how good the developer, but also efforts to find defects in his code.

Attitude 3: Do not compromise on test quality issues

Just like code quality, testing requires high quality. Excellent testers should not make any compromises in the quality of their tests.

Attitude 4: Thankful to the developer

It is possible that code written by great developers does not contain any flaws. Incredible? If so, then thank the developers.

If the code written by the developer is not flawed, good testers should thank and respect them. It should be remembered that his friend is more than just a flaw, and developer should be his friend.

Attitude 5: I'm no worse than the developer

In the field of testing, is not there a lot of people think lower than the developer? I believe there are many such people. If the tester feels lower than the developer, he does not actually do the test properly. As mentioned earlier, developers and testers work in the opposite direction, but have the same goal of producing high-quality software.

If you want to be a good testers, you should be proud of your work first, do not feel inferior.

Attitude 6: More than developers know

How many testers know more about technology and architecture than developers? Probably not too many. As testers, the job content should not be just writing and executing test cases and reporting bugs. He should know more technically than the developer, and only in this way can you know where you can break the software and find the flaw.

Excellent developers and testers in addition to the superb technical skills, but also have a professional attitude, I hope Raghuraman summary to help you.