mostraligabue
» » Bug Proofing Visual Basic: A Guide to Error Handling and Prevention

ePub Bug Proofing Visual Basic: A Guide to Error Handling and Prevention download

by Rod Stephens

ePub Bug Proofing Visual Basic: A Guide to Error Handling and Prevention download
Author:
Rod Stephens
ISBN13:
978-0471323518
ISBN:
0471323519
Language:
Publisher:
Wiley; 1 edition (November 30, 1998)
Category:
Subcategory:
Programming
ePub file:
1892 kb
Fb2 file:
1836 kb
Other formats:
lit lrf mobi txt
Rating:
4.4
Votes:
852

Bug Proofing VISUAL BASIC(r) Let's face i. 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

Bug Proofing VISUAL BASIC(r) Let's face i. 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.

Bug Proofing VISUAL BASIC(r) Let's face it, most programs with more than ten lines of code contain bugs. And as you know, the longer a bug exists in a system, the harder it becomes to locate and repair.

Bug Proofing Visual Basic book. Goodreads helps you keep track of books you want to read. Start by marking Bug Proofing Visual Basic: A Guide to Error Handling and Prevention as Want to Read: Want to Read saving. Start by marking Bug Proofing Visual Basic: A Guide to Error Handling and Prevention as Want to Read: Want to Read savin. ant to Read.

Rod Stephens started out as a mathematician, but while studying at MIT, he discovered how much fun algorithms ar. Bug Proofing Visual Basic: A Guide to Error Handling and Prevention (Wiley Computer Publishing) by Rod Stephens (5-Jan-1999) Paperback Jan 1, 1600

Rod Stephens started out as a mathematician, but while studying at MIT, he discovered how much fun algorithms are. He took every algorithms course MIT offered and has been writing complex algorithms ever since. During his career, Rod has worked on an eclectic assortment of applications in such fields as telephone switching, billing, repair dispatching, tax processing, wastewater treatment, concert ticket sales, cartography, and training for professional football players. Bug Proofing Visual Basic: A Guide to Error Handling and Prevention (Wiley Computer Publishing) by Rod Stephens (5-Jan-1999) Paperback Jan 1, 1600.

Bug Proofing Visual Basic : A Guide to Error Handling and Prevention. By (author) Rod Stephens.

Download PDF book format. Uniform Title: Microsoft Visual BASIC. Choose file format of this book to download: pdf chm txt rtf doc. Download this format book. Bug proofing Visual Basic : a guide to error handling and prevention Rod Stephens. Book's title: Bug proofing Visual Basic : a guide to error handling and prevention Rod Stephens. Rubrics: Debugging in computer science. Download now Bug proofing Visual Basic : a guide to error handling and prevention Rod Stephens. Download PDF book format. Download DOC book format.

2011 IEEE 35th Annual Computer Software and Applications Conference Workshops.

Stephens, Bug Proofing Visual Basic: A Guide to Error Handling and Prevention, John Wiley & Sons, 1998. Mobile Security and Privacy. Help is here! Packed with code, this practical guide shows you how to write effective, error-free programs and, best of all, how to test your programs at crucial stages of development. You'll find out how to handle unexpected bugs that do occur and how to locate and fix them quickly.

Visual Basic Error Handling. DebeG used Ask the Experts™ Rod Stephens wrote a great book that covers LOTS of stuff about error. DebeG used Ask the Experts™. Microsoft Development. Visual Basic Classic. I am looking for a web site that has some really good ideas for handling errors in VB applications. I find it very difficult to pinpoint where errors are happening in VB code and thought that there might be a better way to handle them than just displaying the error number and description. This isn't always helpful in large subroutines. Rod Stephens wrote a great book that covers LOTS of stuff about error handling called "Bug Proofing Visual Basic. His web site is ww. b-helper. I just tried it myself and it appears to be down today.

Prevent program bugs right from the start and quickly exterminate existing ones! Bug Proofing VISUAL BASIC(r) Let's face it, most programs with more than ten lines of code contain bugs. And as you know, the longer a bug exists in a system, the harder it becomes to locate and repair. Help is here! Packed with code, this practical guide shows you how to write effective, error-free programs and, best of all, how to test your programs at crucial stages of development. You'll find out how to handle unexpected bugs that do occur and how to locate and fix them quickly. You'll get bug prevention and repair techniques that just aren't available anywhere else! You'll get the kind of advice and information that usually only comes from years and years of hard-won experience! You'll find out: * How to design bug-free programs * How to code proactively to prevent bugs before they start * How to write code that exposes bugs instead of hiding them * How to catch bugs before they do any serious harm * How to find bugs using tools like the debugger and code profiler * How to use debug and runtime versions of a program to make debugging easier * How to use On Error statements to handle unexpected conditions * How to record information automatically, so you can fix bugs after users encounter them * How to use proven methods to find errors quickly * How to create and analyze special foolproof tests for errors
  • 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!

  • I get to review a lot of books on VB and while some general VB books give basic tips on trapping bugs, none really gives the coverage of this important subject that this book does. This book is devoted in its entirety to avoiding, exposing and reducing bugs. The author discusses the various debug tools as well as ways to prevent bugs by using good programming practices during design, coding and documentation. He draws on his experience as a programmer to identify areas that are prone to produce bugs and shows ways to 'bug proof' these trouble spots. In fact the book is full of hard won 'tips' based on the authors experience that can save you lots of grief if implemented in your development strategy.
    Unless you are an experienced VB programmer -or you just want to join the legions of software developers shipping half complete, buggy products that need a new patch every week- I recommend that you buy this book. I read a recent article in 'PC World' that commented on the large amount of developers shipping crappy, bug-ridden products and this lack of quality is a real problem so time spent learning to improve the quality of your programs is time well spent.

  • This book gives a lot of tips but most of them are pretty thin on substance. Specifically, there is very little information particular to VB hazards or how to write an industrial strength error handler in VB. I think I expected more substance coming from an author who's previous books have been fairly advanced. If you are a beginning programmer this book is great. If you are an experienced programmer this book will be a quick read and you might get a tidbit or two that will save you the cost of the book.

  • I love this book. It is written in a clear, understandable, and logical style.
    The author discusses a logical convention of how programmers may write their code so that it will be readable and understandable by the next programmer who may not be as knowledgeable. By using properly descriptive variables, clear comments, straight-forward code styles, and no corner cutting, an application can be debugged easily by another programmer long after the first programmer has left the company. This would be good for department managers in establishing project standards for multiple programmers.
    Furthermore, logical methods are explained for capturing bugs that can be kept in or deleted from the compiled code without having to manually delete code lines before a compile. Rod Stephens's techniques have prevented me from making mistakes that it would take a professional programmer years to learn.
    Finally, his website shows all of the errors in his book (very few) and provides downloads of all of the code including improvements in the end-of-chapter questions.

  • I have several of Rod Stephen's books. Whenever I start with a new client I bring along my copies of his books on algorithms and graphics. When I saw this book I had to buy it. I am not disappointed. He spends time writing about how to verify the data. He writes clearly and points out some of the obscure problems and our assumptions within Visual Basic. He makes sure that we know that when we write code we are not writing just for the computer, but for other people (sometimes ourselves).

  • This is one of my all-time favorite books. I only wish Rod Stephens would re-write it now as a language-agnostic (or VB & C#) book. So many of the concepts have much broader applications than to just VB, and so many people would benefit from this book that will never have the chance.

    This is the number one book for how to write *maintainable* code. This is the book that you'll wish *every other* programmer would read. In fact, I'm going to go re-read it now, to ensure I'm a good coding citizen...

  • 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.

  • The rule format of the book is a great way to learn how to write good code. You find yourself quoting the book while your coding. Covers heuristics that many "self taught" programmers cannot learn anywhere else.