10 easy ways for programmers to hate you – Medium

Warning: This article needs to be read carefully!

If you are in software testing or software development, you may know a few things about the relationship between “tester and coder”. I don’t know who started the previous war or how their relationship got worse, but it is clear that the tester and coder often don’t like each other. Coder basically doesn’t like tester, but what if I tell you that you can make them hate you more?

In this article, I will share with you 10 easy ways for coder to hate you more. Wait a minute … I’ve had enough problems with my coder, do you want to share tips that will destroy that relationship forever ???????

I don’t know, that’s what you understand what I try to convey through this article. No problem, let’s go.

1: Submit a bad error report

Want to make the coder hate you right away? Report an important problem but vague or incomplete information so they have no idea about the problem. Like this:

Summary: System crashes

Description: The crashes system on my several times PC. Fix it like that

Steps to reproduce: None

Observed result: None

Expected result: None

A report like this will make your coder frustrate immediately.

Why can this make them hate you? We all know that the coder depends a lot on the error report of the tester to understand the error and correct it. If you are sending them a bad report, they will be difficult or take a long time to re-create and fix bugs.

2: Critics of developers about errors encountered

Coder always feels bad when you find a problem in their code. You may have made them feel worse when pointing out exactly who wrote the code that caused the error. Sayings like:

• I think you should work better after handling this bug.
• I think this is a stupid design that you did.
• The programmer did not correctly handle this exception?
• Why does this function not work?
• ……

Constructive feedback only makes the coder more like you, so give up destructive feedback like above.

3: … Public criticism

You want things worse? Don’t just criticize them but do it publicly. You can point out the responsibility for a specific programmer in the bug tracking system (such as Redmine, Jira …) where people can read your comments and reviews. You can also do this in group meetings and especially with the relevant management team. Why should I do this? That’s because you are touching one of the sensitive parts of the coder. That is their instinct.

4: Incorrect test environment

It requires the tester to check the system and report the problem in the appropriate environment. Do you want to surprise the developer, try this:

1. The Coder build gives you a new test environment
2. You mark the old test environment and start working on it.
3. The next morning, you rush to meet the coder and notice that you found an error on the build yesterday.
4. Then you re-show him the error on your computer.
5. The coder then takes all day to analyze, re-create the bug you pointed out. Until the end of the day he found out that you had tested the build wrongly.

Hura hura you did that, and now the developer will remember your name for the rest of his life.

Read More…