What you want-programmers and testers

There seems to be a quarantine bar between the programmer and the tester. Maybe I am too sensitive ......

Starting from the current division of labor in the company, I have heard many people complain to me. From Requirement Analysis to product delivery, a project in a small company is usually handled by one person, this is true even for some large companies.
It also includes testing. In this case, there is no so-called division of labor. It is nothing more than a single player. Naturally, there is no distinction between cooperation and positions. If the tester and programmer are not alone
It seems very common for programmers to hand over a considerable amount of testing work to testers, but it actually makes sense. The main focus of programmers is to focus on coding rather than testing, in a sense, the tester
This reduces the workload of programmers and helps them focus more on writing programs.

In an ideal situation, programmers are only responsible for coding. Of course, this seems unrealistic. Generally, some white-box tests are also completed by the programmers themselves. The tester is responsible for all the tests, and send it to programmers
Report any possible problems. So far, I have stayed in several companies and have applied for several companies. It seems that it is not easy to cooperate well between testing and programmers.
There are many other reasons for communication, such as technical background and experience.
In the software industry, there seems to be a saying that the tester is an entry-level position, just like the PCB in the hardware industry.
The same is true for engineers in Layout? A good test should be technically familiar, otherwise it is difficult to accurately analyze some hidden bugs. But what does technology mean? Meaning
There must be considerable software development experience for testing, but how many programmers are willing to perform testing after n years of development? In the programmer's mind, it seems that the tester does not have a high job as a programmer.
There is no good programmer. In some companies, the tester is more stressed than the programmer, so the conflict arises. The tester seems to always be a tester, always at the entry stage, a lot of projects with a lot of experience
Programmers can either switch to companies with better treatment as programmers or senior programmers, or simply go to work as project managers or even start their own companies. It seems that no one is willing to go back to a "entry-level" position.

I remember when I went to a company for an interview some time ago, a tester asked me which side of the question I heard when there were disagreements between the tester and the programmer? In my opinion, the tester should listen to the test if the technology is feasible, because
In a sense, it is equivalent to a user. If the test fails, how can it be used by the user. But in the end, some tests thought that I was hypocritical and fainted. I was always a real person.
What about hypocritical people? Looking back, the test may think that a programmer is more weighted than him. No matter whether he is willing or not, he still needs to listen to the programmer at the end, so he will think that I am hypocritical and understandable, but I
I didn't think that even the tester was a little debelited and speechless ......

In fact, at any time, I tell myself that we must treat people equally, especially our colleagues, on the premise that others treat me like this. As a programmer, it is important for testers to be equal and respectful. Because
What they do is to make our "works" more perfect, so that customers will be more satisfied, which is a manifestation of teamwork.

Programmers should not blame testers at any time. testers are also people, not sages. They also make mistakes, even if they do not test bugs, the programmer should also fill in only one test feedback record
INVALID is over, and should not be in front of or behind the scenes because it is a programmer's professional ethics. To become a good programmer, we must first learn how to treat everyone in the team with different opinions.
It is a normal thing, but pay attention to communication. Of course, I am not saying that quarrel is not allowed. One thing you need to understand is that sometimes quarrel is also a manifestation of cooperation.