Home
Search
 
What's New
Index
Books
Links
Q & A
Newsletter
Banners
 
Feedback
Tip Jar
 
C# Helper...
 
XML RSS Feed
Follow VBHelper on Twitter
 
 
MSDN Visual Basic Community
 
 
 
 
 
 
  Bug Proofing Visual Basic: Discussion: Rigorous Design  
 
Overview Table of Contents Updates
Source Code Comment Templates Sample Text
Discussion, Q & A Wiley Barnes & Noble
 
 
 

Naming Conventions

12/29/98 Scott Carpenter started this discussion with:

    The most challenging part of the book for me personally is your call for more rigorous design, testing, and documentation. Like most developers (I'm guessing most), I find it more fun to just jump in and code. I'd be better served both at Cargill and in my independent pursuits by a more structured approach. I'll probably purchase another copy for work - I spent some time pitching it to a team member today.

12/30/98 My response:

    You're absolutely right. It takes a lot of discipline to prepare properly before coding. Because mistakes early have such a huge impact, however, it is worth almost any effort to prevent them. This is most important in big projects and I confess I do not always practice what I preach in small projects. For example, the HowTo's on my Web site. Or even a lot of programs in my books. They are intended to get readers started and too much error handling hides the key concepts.

 

 
  Bug Proofing Visual Basic: Discussion: Rigorous Design  
 
Overview Table of Contents Updates
Source Code Comment Templates Sample Text
Discussion, Q & A Wiley Barnes & Noble
 
 
 

Copyright © 1997-2010 Rocky Mountain Computer Consulting, Inc.   All rights reserved.
  Updated