I'm a front-end developer, but I think the story resonates with any developer who's been feeding you a bug. "The light on the 26 floor meeting room is lit. It needs to be extinguished. "You should be able to get it done in 5 minutes, just click on the switch," wrote the note in the bug. "You went to the conference room on the 26 floor. The light was on, but there was no light switch in the room. So, you're ready to install one. But the designer said it would spoil the beauty of the room. In addition, the walls are concrete. You need the right tool to install the switch. However, no one will approve the purchase of these tools. If there is no suitable tool, the installation switch will take two days. They want you to turn off the lights right now because they're afraid the CEO might decide to go to the 26 floor on a whim and pass through the conference room and ask why the lights are on. Now you are constantly receiving e-mails asking why the room lights are still on. Now that you have to send an email stating the situation, several people started a panic e-mail chain. You know, if you expect the problem to be addressed by email (and not actually do something), the problem will never be fixed. Bug system, this bug is handled by you, and its deadline is today. If the problem is not solved, there will be trouble for you. So, you managed to get into the ceiling of the corridor on the 26 floor and found the cable for the meeting room lights and cut it off. The problem is solved. To quell the panic in the e-mail chain, you (mass mailing again) explain how you solved the problem. The mailbox was quiet for a while. When it rang again and again, everyone was worried that the room lights could not be turned on and off now. What if the CEO wants to have a meeting there? So they asked you to "pull the light wire into the basement." When someone needs to switch the lights on, they will notify you to go to the basement to connect or disconnect the wires. You protested this ridiculous solution. Your boss says, "Yes, I know it's not ideal." But it is now the only solution. "At this point, you face the choice. You can do as they say, or resign to protest and seek a job. But you know, once you start a new
work, the new they will probably also ask you to do such an idiot thing, if not more idiot. You pulled the wire from the 26 floor to the basement. When you get into the basement, you find that there are dozens of of wires hanging on the wall, you know you're not alone, and you know where this idiot idea came from. You have adjusted the wires, mark the personnel, and silently apologize to the man who is likely to deal with it. Finally, you go back to your desk and you receive a new report. QA re-opened the bug. The bug description says, "The room is still lit." "You go back to the conference room on the 26 floor. The lamp was extinguished. You go back to your desk and close the bug, stating that you have checked it yourself. QA re-opened the bug again. "The room is still lit" in the bug description insisted. Once again, once you have confirmed that the bulb is out, you report the situation to your boss. He suggested you go to the basement to check the wires. You protested that you were deep silence at the light, it was extinguished. "I know, but check it out." This way you can tell QA that you have confirmed all the processes. "You sighed and went to the basement. Sure enough, the wires were not connected, and the ends of the incisions were properly wrapped. They cannot conduct electricity in any way that you can understand. You give QA feedback, you check the wires, they're not connected, you're looking at the bulb, it's off. "I don't mean the light bulb," QA said. "The light in the room is described in the bug. The room is still not dark enough now. You should pull down the blinds. "You responded by saying that the blinds don't belong to you, and the bug describes the lights. QA doesn't believe you, issue a set of emails asking if the bug contains blinds. You waited a while, and the mailbox rang again. "Theoretically," they asked, "If the light is too bright or too dark, can a person who meets in a conference room on the 26 floor be free to pull up or pull down the blinds?" "Yes, they can, you reply." "Can any ordinary person do it?" Don't they need you to do it? "Yes, any ordinary man." No, they don't need you. Anyone can do that. "It's great. So the light problem is over for the time being. I'll arrange how to handle the blinds for the meeting. "The bug was closed. Now, the CEO may have felt something from all the discussions on the 26 floor conference room, hoping to have a meeting there. You've got a few panicked emails hoping to turn on the lights. You go to the basement, connect the wires, and return to your desk. You have 32 more new messages in your Inbox. "It's a problem-the lights are off!" There's a problem-no lights! " "Did you get the E-mails we sent?" Wait, wait. The 32nd e-Mail said: "Nothing-the light is on." "This (32 mail) process, more or less, occurs repeatedly on switching lights. If there's any good news, it's the end of the meeting., we even forget that there is a conference room on the 26 floor and you don't need to do anything about it.
A bug that developers face (go)
