Top 24 replies by programmers when their programs don't work:

-

Top 24 replies by programmers when their programs don't work:

24. "It works fine on MY computer"
23. "Who did you login as ?"
22. "It's a feature"
21. "It's WAD (Working As Designed)"
20. "That's weird..."
19. "It's never done that before."
18. "It worked yesterday."
17. "How is that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it's not been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?"
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"
1. "I thought I fixed that."

Comments

vipin kumar said…
Blog comment
Thank you for sharing valuable information. Nice post. I enjoyed reading this post. The whole blog is very nice. I found some good stuff and good information here Thanks.Also, read my blog about Bugs software testing

December 19, 2023 at 9:38 PM
Investing in Paradise said…
This comment has been removed by the author.
September 3, 2024 at 2:48 AM
Beautyspa said…
The Best software testing company in Noida . My company is precise testing solution pvt Ltd best services provided in software testing and cyber security Vapt testing and Stqc and Cert-in. IVapt testing company in Noida
September 13, 2024 at 3:19 AM
Matt Calder said…
Every developer has probably said at least half of these at some point. What’s interesting is that behind the humor lies a serious truth: many of these excuses are symptoms of gaps in testing, communication, or traceability. When teams rely only on local setups or ad-hoc checks, bugs slip through and become “mysteries” in production. The shift happens when testing becomes systematic, repeatable, and visible across the team. That’s where disciplined processes — and tools like test management software — make all the difference, turning those excuses into opportunities for prevention rather than damage control.
October 3, 2025 at 5:47 AM
Post a Comment

Popular posts from this blog

Cyclomatic complexity

-
Cyclomatic complexity is a software metric (measurement). It was developed by Thomas McCabe and is used to measure the complexity of a program. It directly measures the number of linearly independent paths through a program's source code. It is computed using a graph that describes the control flow of the program. The nodes of the graph correspond to the commands of a program. A directed edge connects two nodes if the second command might be executed immediately after the first command. Definition M = E − N + 2P where M = cyclomatic complexity E = the number of edges of the graph N = the number of nodes of the graph P = the number of connected components. "M" is alternatively defined to be one larger than the number of decision points (if/case-statements, while-statements, etc) in a module (function, procedure, chart node, etc.), or more generally a system. Separate subroutines are treated as being independent, disconnected components of the program's control flo...
Read more

Appium Configuration with Visual studio for selenium C# development

-
Prerequisites: 1. Visual Studio Ultimate (2010 or above) (Because MSTest is present in that) 2. Android SDK For Windows (Download Link) (Website link) 3. Appium For Windows (Website Link) (Download Link) 4. A Real Android Device running Android 4.2 or Above 5. A USB Cable to attach your Android Phone to Your PC. 6. ADB Interface Drivers for your device (Link on how to get that ) (very important Step) Some Configurations for Android SDK and Appium: • When you have installed Android SDK, go to My Computer, right click, click Properties, click Advanced System Settings, and click Environment Variables. • Create a new User Variable with the name “ANDROID_HOME”. Give path to your sdk folder in the value. The default path is C:\Program Files (x86)\Android\android-sdk • Edit the PATH variable in “System Variable” Section. Append the path to your tools folder and platform-tools folder. Separated with “;” The paths are C:\Program Files (x86)\Android\android-sdk\tools C:\Program Files (x...
Read more