I can reinforce each lesson/problem you're describing one by one through the exercises, but a new person simply wouldn't know good code if it slapped them in the face.
that is my point: your readers might not understand everything you're doing, so they're just going to copy and paste parts of it into their new projects. if you give them sloppy code to learn from, they're going to copy that sloppiness into their code that makes its way into the real world.
there are a lot of things in c that new programmers have to be especially careful about that aren't relevant to python.
Retracted.
This confuses me. How can you teach someone to do something if you won't do it yourself? Reading your statement literally, you are effectively going to say, "This is how and why to write bulletproof code, but I'm not going to." The whole point of LxTHW is to learn by doing. If you're doing it wrong, they're learning it wrong.
> I'm not qualified to meet that kind of lofty standard anyway.
Then you shouldn't write the book. Honestly. I know you intend to do some good and to be productive, but serving as a teacher and a reference point in an area that you're not qualified in is actually counterproductive.
I'm not saying don't write the book. Get qualified first.
Further, the aim is to teach people how and why to write bulletproof code, not to demonstrate bulletproof CString tutorials.
No such thing as a perfect program, startup, relationship, or book.
Not being perfect is not the same as going in the wrong direction.
I can reinforce each lesson/problem you're describing one by one through the exercises, but a new person simply wouldn't know good code if it slapped them in the face.
Confer with Learn Python the Hard Way to get a feel for the aesthetic and technique I'm working towards.
I don't want to write bulletproof code, I want to teach them how and why to write bulletproof code.
I'm not qualified to meet that kind of lofty standard anyway.