Tim Provencio said
I was trained in VB at a Fortune 1 company (narrows it down, eh?). I developed a very paranoid mindset with my development that I have not seen in others until I came across this book.
It really took the beliefs and habits that were instilled in me and materialized them into a book. I can then take this book and recommend it to folks I have to share projects with to spread those beliefs and habits without seeming like a pain.
If you aren't an enterprise class developer but would like to play one on TV by coding tight apps, get this book. Your team members/users will love you for it!
Eric D. Burdo said
This book is a must have.
If you have ever written anything in VB, then you know how much of a pain Error Handling is. This book will give you a solid foundation of how to handle errors. It also gives you lots of insight into handling general error or specific errors, and writing bug-proof code.
Lawrence said
A very reasonable book for someone to refresh the knowledge and fill the gaps about error handling in VB. It does provides the stuff that is missing in the VB help or other VB books. At least it provided some guidance on how to tackle the error handling within a program, instead of a routine only. Photocopy the content page and use it as a quick reference. One little shortcoming is that the author sometimes repeats his message in many places in the book.
said
I found this book to be only for beginners. It is very repetitive about a lot of stuff that you just know if you have programmed for more than a month. Most of the suggestions it makes are pointless or just too obvious, and i can't believe you can write so many pages with so little content. In conclusion, if you have used Visual Basic for more than a month, you must NOT buy this book, it wont help in the littlest bit. Please excuse my English if i've written something wrong.
said
Sorry, I read this book, but didn't think much of it. I was able to pick up a few valuable tidbits, but overall thought the book's title and promise didn't deliver.
Avoiding bugs, it seems, has much to do with following good programming practices and perhaps that should have been the book's title. Much wasted time is spent on telling us how to indent lines of code, how to line up our comments, and admonitions to fix our own bugs and to be alert when you test.
There was 20 pages of good stuff and the rest was fluff. It was as if Rod Stephens needed to put out a book fast and just shotgunned his many years of programming experience at us, hoping something would stick and save us from having too many bugs.
I realize I now own 4 of his books, but none are even in my top 10 Visual Basic books. If I could have read the book first and then paid for it, I would have paid 5 bucks.
Comments