3 ms·
If you're not qualified to meet that standard then don't write a C book (or learn more before you do). C programs are either bulletproof or they are a hazard.
by fauigerzigerk 16y ago
If you're not qualified to meet that standard then don't write a C book (or learn more before you do). C programs are either bulletproof or they are a hazard.
- jimwise 16y agoOn the bright side, forcing yourself to write bulletproof code for the book may well be the best way to become qualified.
- alnayyir 16y agoOn the dot.
- fauigerzigerk 16y agoIf I understood him correctly he said that he didn't want to try to do that.
- alnayyir 16y agoSort of, I'm not going to try to write perfect code, but I will make myself a better programmer by doing this. Further, the aim is to teach people how and why to write bulletproof code, not to demonstrate bulletproof CString tutorials.
- alnayyir 16y agoThe unwillingness to do for fear of violating some perfect model leads to never making progress at all. No such thing as a perfect program, startup, relationship, or book.
- fauigerzigerk 16y agoI'm not saying you shouldn't write the book because it might not be perfect. I just disagree with your concept for the book. I think readers must see good code even if they don't understand immediately why it is good code. C programs that aren't really good tend to be really bad because they crash or worse. Not being perfect is not the same as going in the wrong direction.