MobileRead Forums - View Single Post - Audio (video) - Kindle. Getting it up and running, Code level.

geekmaster · 07-12-2012, 03:06 PM

You do not need error handling to tell you that you are stupid. It is not mission-critical or life-critical code after all. If it does not work, go RTFM, and fix it.

The code posted above is less likely to send the reader away screaming in horror.

EDIT: Actually, I do START with error handling code (until I get it working), then I strip that out of the working parts that no longer need it. By the time I publish it, any residual error handling code is only there as a fallback to workaround hardware for firmware issues.

EDIT2: Of course, in my PROFESSIONAL code, in some places there is much more "error handling" than algorithm. And when deviating from "standard methodology", I include a rationale commentary for why that deviation was needed and what are the consequences of altering it. I also include embedded references throughout my code showing WHERE I got my ideas, to prove that they are unencumbered by patents or viral licensing. But I still minimize white space though (maximum "above the fold" content for readers who rarely use scrollbars or cursor keys).

EDIT3: Now that K5 sound works, it is time for the "Touchscreen Stylophone" I mentioned earlier.

07-12-2012, 03:06 PM	#143
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773668 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	You do not need error handling to tell you that you are stupid. It is not mission-critical or life-critical code after all. If it does not work, go RTFM, and fix it. The code posted above is less likely to send the reader away screaming in horror. EDIT: Actually, I do START with error handling code (until I get it working), then I strip that out of the working parts that no longer need it. By the time I publish it, any residual error handling code is only there as a fallback to workaround hardware for firmware issues. EDIT2: Of course, in my PROFESSIONAL code, in some places there is much more "error handling" than algorithm. And when deviating from "standard methodology", I include a rationale commentary for why that deviation was needed and what are the consequences of altering it. I also include embedded references throughout my code showing WHERE I got my ideas, to prove that they are unencumbered by patents or viral licensing. But I still minimize white space though (maximum "above the fold" content for readers who rarely use scrollbars or cursor keys). EDIT3: Now that K5 sound works, it is time for the "Touchscreen Stylophone" I mentioned earlier. Last edited by geekmaster; 07-12-2012 at 03:20 PM.