For organizations to develop software successfully -- and for individual programmers to succeed in team development projects -- high-quality development standards are essential. The Visual Basic Style Guide brings together state-of-the-art guidelines for professional development geared specifically toward VB environments, and organized as patterns that provide specific solutions to the most common problems VB developers encounter. Tim Patrick, whose lengthy experience as a VB developer includes the creation of in-house development standards guides, covers every aspect of the VB project lifecycle. The Visual Basic Style Guide addresses planning, requirements gathering, coding, documentation, user interfaces, and much more. Wherever commonly accepted standards exist -- such as the Hungarian naming conventions supplied with the VB documentation and the user interface norms detailed in Microsoft's Windows Interface Guidelines for Software Design reference -- Patrick builds on them. Where standards do not exist, Patrick presents coherent, disciplined recommendations for building systems that will effectively respond to user needs, offer superior reliability, and are far easier to maintain.
Book Description
Editorial Reviews
From the Back Cover
The essential companion for Visual Basic development teams and individuals.
* Master effective practices to create crystal-clear, reusable code
* Foster effective collaboration by maintaining reliable standards
* Acquire the mindset of a professional developer
* Use the comprehensive reference section to make your programs consistent and portable
* Works with all flavors of Visual Basic
* Professional best practices for programmers
* Guidelines for standard structure and syntax
* Foundational attitudes of quality development
* Complete reference section for all flavors of Visual Basic
The essential companion for Visual Basic development teams and individuals.
All effective teamwork is based on clear communication. In the field of software development, this means using consistent, documented conventions that can be easily understood and built upon by teammates, now and in the future.
To meet this need, this handbook for Visual Basic programmers contains a comprehensive reference section covering nomenclature, instantiation, keywords, controls, user interfaces-every major VB concept, in all flavors of VB. And more than that, it promotes an attitude, an environment of the mind in which healthy Visual Basic programs are formed.
The winning philosophy of The Visual Basic Style Guide will help your team develop its programming power through discipline, documentation, and professionalism. Build your development skills through:
* Application of proven and consistent style and user interface methodologies,
* Grounding in the foundational attitudes of discipline, planning, and ethics, and
* Getting to know the comprehensive, quick-access reference section.
Even programmers working on individual projects will benefit from the enhanced professionalism that comes from consistency. Whether you're a experienced programmer, a team leader, or a manager, you'll appreciate the thorough coverage and the rigorous standards provided in The Visual Basic Style Guide.
About the Author
Tim Patrick is a Visual Basic software engineer in Redmond, Washington, with nearly 20 years of programming experience. The ideas presented in this book grew out of his experience with both troubled and successful development projects. He is a graduate of Seattle Pacific University.
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
7 of 8 people found the following review helpful:
5.0 out of 5 stars
Great Supplemental Book to Software Design Education,
This review is from: The Visual Basic Style Guide (Paperback)
This book is a great complement to any beginning Visual Basic software developer's education in software design. The concepts in this book help organize the approach one should take in creating Visual Basic applications that will be more adaptable, extensible, and maintainable. I am already putting these concepts to practice and seeing positive results.
4 of 4 people found the following review helpful:
2.0 out of 5 stars
Very weak,
By A Customer
This review is from: The Visual Basic Style Guide (Paperback)
The reviewer from Charlotte was right about this book being disappointing. I bought it but am going to return it. The content is very elementary. I bought it on the hope that there were tips specific to Visual Basic. There are a few, but any of these tips can be found in a good Visual Basic programming book. I also agree with the Charlotte reviewer that the keyword reference is just filler; it is inexplicable in book of this type.The book also advocates Hungarian notation (preceding each variable by a prefix indicating its type such as strABC for a string.) I am not fond of Hungarian notation. I agree with Francisco Balena, (Programming Microsoft Visual Basic 6.0) that it makes the code difficult to read. I would have preferred that the author present this notation as an option only, not as the only way to go. The anecdotal style evidenced in the passage printed above ... is also typical. Its seems pleasant at first but soon becomes tiresome, more applicable to a leisurely article in the Sunday paper than a book about programming.
5 of 6 people found the following review helpful:
3.0 out of 5 stars
For Beginners Only,
By
Amazon Verified Purchase(What's this?)
This review is from: The Visual Basic Style Guide (Paperback)
I was disappointed in this book. While the cover clearly indicates the intended audience is between Intermediate and Advanced, I'd place it pretty close to Beginner. It is really geared toward the person who knows enough about VB to make some things work, but wants to refine his/her coding style. If you haven't learned this stuff by the time you reach Intermediate, you've probably already developed a lot of bad habits.Also, the reference section just seemed to be filler. Why should a style guide have a keyword reference? It takes one third of the whole book. If I wanted a keyword reference, I would have bought one. What little valuable information he adds could have been done in 20 pages instead of 150+. As long as you want a book that is geared closer to beginner than intermediate and you don't mind some fluff, then this book is okay.
Share your thoughts with other customers: Create your own review
|
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
