Skip to main content

Top 25 Explanations by Programmers when their programs don't work

I found this list absolutely hilarious.  I've starred the ones that I use the most.  :)


Top 25 Explanations by Programmers when their programs don't work:
1. Strange...  ****
2. I've never heard about that.
3. It did work yesterday. **
4. Well, the program needs some fixing.
5. How is this possible? ******
6. The machine seems to be broken.
7. Has the operating system been updated?
8. The user has made an error again. ****
9. There is something wrong in your test data.
10. I have not touched that module!
11. Yes yes, it will be ready in time. **
12. You must have the wrong executable.
13. Oh, it's just a feature. **
14. I'm almost ready. **
15. Of course, I just have to do these small fixes. ****
16. It will be done in no time at all. ***
17. It's just some unlucky coincidence.
18. I can't test everything!
19. THIS can't do THAT.
20. Didn't I fix it already? ******
21. It's already there, but it has not been tested.
22. It works, but it's not been tested. ***** MY FAVORITE!!! *****
23. Somebody must have changed my code. *******
24. There must be a virus in the application software.
25. Even though it does not work, how does it feel? *

Comments

Post a Comment

Popular posts from this blog

Developing a lightweight WebSocket library

Late in 2016, I began development on a lightweight, isomorphic WebSocket library for Node.js called ws-wrapper .  Today, this library is stable and has been successfully used in many production apps. Why?  What about socket.io ?  In my opinion, socket.io and its dependencies are way too heavy .  Now that the year is 2018, this couldn't be more true.  Modern browsers have native WebSocket support meaning that all of the transports built into the socket.io project are just dead weight.  On the other hand, ws-wrapper and its dependencies weigh about 3 KB when minified and gzipped.  Similarly, ws-wrapper consists of about 500 lines of code; whereas, socket.io consists of thousands of lines of code.  As Dijkstra once famously said: "Simplicity is prerequisite for reliability." ws-wrapper also provides a few more features out of the box.  The API exposes a two-way, Promise-based request/response interface.  That is, clients can request dat...
Post a Comment
Read more

Wedding Prediction - October, 2013

Carla and I are planning on getting married sometime in October next year.  We need to pick a date, and that decision may  involve some science and mathematics.  :) For example, we want the weather to be nice.  To be more precise, we'd like the high temperature for the wedding day to be between 60 and 80 degrees Fahrenheit.  Obviously, we have both lived in Ohio our entire lives, and we have a pretty good idea of what the weather will be like.  We both hypothesised that October was a "hit or miss" sort of month; it could be cold, or it could be nice. But, for me, a simple hypothesis was not enough; I really wanted to know the probabilities of decent weather based on historical weather data.  Many websites on the Internet (i.e. almanac.com) charge you to review historical weather data, but Carla and I discovered a cool page on cleveland.com that provided exactly what we wanted.  I loaded the historical temperature data from 1903 to 2011 f...
2 comments
Read more

Data Persistence in Various Databases

This blog post will cover the varying levels of data caching and data persistence provided by various operating systems and database systems. Cache  - A device placed in front of another storage device that is used for temporary storage of data.  The use of a hardware cache is often transparent to the end user and is generally smaller, faster, and less persistent than the backed storage device.  Rather than reading/writing from/to a slower storage device (i.e. a hard disk), we read/write from/to the cache (i.e. RAM, NVRAM, etc.). Reading from a cache is simple.  If the datum we requested is in the cache, we simply read it from the cache.  If not, we need to retrieve the datum from the storage device and place it into the cache (often a much slower operation). There are different policies when we write to the cache, though... Write-Through Cache Policy  - When using this policy, writing over the cache also writes over the data on the backed storage d...
Post a Comment
Read more