Sorry for the typo, Dennis!
Well, this is what happens when you're typing faster than you're thinking, which in my case doesn't always require a high words per minute rate!
In my comments below, I insist on spelling Dennis' name "David". Mind you, I'm sure there are some remote corners of the world where this is a perfectly acceptable spelling, but I'd be hard pressed to point them out on a map. Unfortunately, I haven't figured out how to edit the post, so we can now add, er, spelling skills to the ever growing list of things I need to improve on.
Sorry 'bout that, Dennis! (insert sheepish grin here as I stare at my shoes...)
From the author
The fact that my development skills have improved over the years is due in large part to the kindness of more accomplished programmers, who were willing and patient enough to teach me their tricks and show me the ropes. I'm finding that to be true in my writing as well.
David not only points out a number of things that I hadn't considered from my own perspective, he does so in a constructive and eloquent manner. One of the best examples of this is his observation that the information in this book can help management to better understand the developer mindset. Er, that is, it might if I hadn't done everything but sic a rabid attack Chihuahua on anyone who even remotely resembles management. Oops...
In any event, this is just one more example of seasoned developers who are kind enough to help others, even if the words aren't always easy to hear. If my books and seminars continue to improve, it will be in no small part due to what I learn from my peers in this business.