Top 10 replies by programmers when their programs do not work
10. “That’s weird…”
9. “It worked yesterday.”
8. “It must be a hardware problem.”
7. “What did you type in wrong to get it to crash?”
6. “There is something funky in your data.”
5. “You must have the wrong version.”
4. “Somebody must have changed my code.”
3. “Did you check for a virus on your system?”
2. “You can’t use that version on your system.”
1. “IT WORKS ON MY MACHINE!”
–
Photo courtesy of agea_blog.
Related posts:
- Why Crunch Mode Doesn’t Work: 6 Lessons Lesson One, then, is this: Productivity varies over the course of the workday, with the greatest productivity occurring in the first four to six hours. After enough hours, productivity approaches...
- Deploy a Rails 3, Sqlite3 application in Tomcat using JRuby and have a Ruby version running side-by-side. A few months ago I got interested in JRuby while researching for text mining algorithms. I found some gems but they are either...
- Coding gems 21-30 #21 A well-written code is a joy to write and a joy to read. #22 If you can’t explain something to a six-year-old, you really don’t understand it yourself. Albert...
- Coding gems 1-10 #1 The more dogmatic you are about applying a design method, the fewer real-life problems you are going to solve – P.J. Plauger #2 Let Ruby be Ruby. Let Java...