The Visual Basic Style Guide
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
- Paperback | 365 pages
- 177.8 x 233.68 x 27.94mm | 748.42g
- 30 May 2000
- Pearson Education (US)
- Prentice Hall
- Upper Saddle River, United States
- w. figs.
Table of contents
I. STRUCTURE. 1. Professional Programming as Style. Goals of Professional Programming. Meeting the Needs of the User. Meeting the Needs of Your Employer. Meeting the Programmer's Needs. A System for Professional Programming. Structure. Foundation. Standards. Summary.2. Using Declaration. What Is Declaration? Why Declare? Clarity. Consistency. Expectations Fulfilled. Increased Recognition. Reduced Memory Usage. Visual Confirmation. How to Use Declaration. Variable Data Declaration. Constant Data Declaration. Other Declarations. Order of Code. Summary.3. Commenting and Style. What Are Commenting and Style? What Is Commenting? What Is Style? Why Use Commenting and Style? Why Include Comments? Description of Purpose. Readability. Second Memory. Logic Clarity. Identification. Code Reviews. Future Modifications. Why Use Style? Readability. Grouping of Logic. Guarantee of Program Flow. How to Comment. Who. What. Where. When. Why. How. How Many Comments? How to Employ Style. Indentation. Capitalization of Identifiers and Literal Strings. Use of Blank Lines within Code. Use of Parentheses around Conditions and Expressions. Use of Line Continuation Characters. Use of Multi-Statement Lines. Automatically Generated Source Code. Summary.4. User Interface Consistency. What Is User Interface Consistency? Consistency with the User. Consistency within the Application. Consistency with Other Applications. Why Maintain User Interface Consistency? Accomplishment of a Task. Access to Information. Increase in Productivity. Increase in Accuracy. Integration with Existing Workflow. How to Maintain User Interface Consistency. Consistency with the User. Consistency within the Application. Consistency with Other Applications. Summary.5. Documentation. What Is Documentation? Why Document? Technical Support. User Support. How to Document. Quality: Always Professional. Style: From General to Specific to General. Content: Types of Internal Documentation. Content: Types of External Documentation. Summary.II. FOUNDATION. 6. Discipline. What Is Discipline? Discipline Is Training. Discipline Corrects. Discipline Focuses. Discipline Perfects. Discipline Affects the Mental Faculties. Discipline Affects Moral Character. Why Be Disciplined? Discipline Results in Professional Programs. Discipline Reduces Development Pressures. Discipline Increases Application Satisfaction. Discipline Prepares You for Advanced Programming. Discipline Attracts the Admiration of Your Peers. How to Instill Discipline. Establishing a Routine. Improving Your Methods. Summary.7. Planning. What Is Planning? Taking the Problem Apart. Putting the Solution Together. Why Plan? Understanding the User's Needs. Standardization. Goals and Milestones. Anticipating Surprises and Risks. How to Plan. Understand What the User Needs. Determine the Project Scope. Organize the Project. Review the Project. Summary.8. Ethics. What Is Ethics? Ethics Is Part of a World-View. Ethics Deals with Right and Wrong Actions. Ethics Deals with Right and Wrong Attitudes. Why Have Ethics? How to Have Ethics. Honesty. Trust. Quality. Ownership. Humility. Summary.III. STANDARDS. 9. Declaration Standards. Nomenclature Standards. Nomenclature for Variables. Nomenclature for Constants. Nomenclature for User-Defined Types. Nomenclature for Enumerated Data Types. Nomenclature for Line Labels. Nomenclature for Procedures. Nomenclature for Declares. Nomenclature for User Interface Elements. Nomenclature Exceptions. Instantiation Standards. Instantiation of Variables. Instantiation of Constants. Instantiation of User-Defined Types. Instantiation of Enumerated Data Types. Instantiation of Line Labels. Instantiation of Procedures. Instantiation of Declares. Declaration Modifiers. Global Options. Compiler Directives. Visual Basic Limitations on Declaration. Data Typing of Literals. Summary.10. Keyword Reference. Categories. Compiler Directives. Conversion Functions. Date and Time Features. Declaration Features. Error Handling and Debugging Features. File System Features. Financial Features. Flow Control Features. Math Features. Miscellaneous Features. Operators. String Features. Alphabetical Keyword List. Summary.11. Control and User Interface Standards. General Considerations. Communication. Control Interaction. Documentation. Specific Control Information. Summary.12. Database Standards. Database Design. Nomenclature. Normalization. Database Documentation. Database Usage. Spreadsheet Presentation. Bound Field Presentation. Form Object Presentation. Summary.Index.
About Tim Patrick
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.