Whenever I see a programming error, I try to imagine the circumstances behind it.
Here’s a “99 bugs in the code” t-shirt.
“Program testing can be used to show the presence of bugs, but never to show their absence.”
~ Edsger Dijkstra
I kinda-sorta like writing code with Sencha Touch and Ext, but I have to say that big problems you encounter with trying to use one tool to write code for multiple platforms are (a) bugs that affect one platform and not another, and (b) trying to write code to some common denominator — when that “common” approach doesn’t look native on any of the platforms.
I write this as various bugs in different cross-platform tools have driven me crazy lately. Some of these are related to Sencha, and some are not, but the end story is that I will tell any customer that if they have the money, they should pay to have native apps on each platform.
In another example of a high-profile software quality problem, Gizmodo reports that a Japanese satellite that was meant to observe black holes was doomed by poor software quality:
“It was only up there a month when something went wrong. A series of unfortunate events caused by both human errors and software flaws sent the satellite spinning out of control.”
Mac Java FAQ: How do I report Mac Java bugs?
I just saw this information on the Mac Java mailing list, how to report Mac Java bugs:
Ant FAQ: How to use echo commands to debug Ant build scripts.
I've been moving back and forth between a ton of different computers lately -- Mac, Linux, and Windows computers -- and I had some problems with an Ant build script. This particular Ant script is complex, and I kept making mistakes, and needed a good way to debug the build process as I set up my application on these different systems.