Re:What do you want to see in Learn C The Hard Way?
by fauigerzigerk on Friday November 05, 2010 @01:04PM
(#1873934)
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.
[ Parent
| on HN ]
Re:What do you want to see in Learn C The Hard Way?
by jimwise on Friday November 05, 2010 @01:42PM
(#1874107)
On the bright side, forcing yourself to write bulletproof code for the book may well be the best way to become qualified.
Re:What do you want to see in Learn C The Hard Way?
by fauigerzigerk on Friday November 05, 2010 @02:28PM
(#1874265)
If I understood him correctly he said that he didn't want to try to do that.
Re:What do you want to see in Learn C The Hard Way?
by alnayyir on Friday November 05, 2010 @02:34PM
(#1874277)
Sort 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.
Re:What do you want to see in Learn C The Hard Way?
by alnayyir on Friday November 05, 2010 @01:56PM
(#1874156)
On the dot.
Re:What do you want to see in Learn C The Hard Way?
by alnayyir on Friday November 05, 2010 @02:02PM
(#1874172)
The 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.
Re:What do you want to see in Learn C The Hard Way?
by fauigerzigerk on Friday November 05, 2010 @02:42PM
(#1874314)
I'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.