Appearance
Practical Standards for Microsoft Visual Basic
This is a very good book for someone looking for a set of standards for writing Visual Basic code. The author covers pretty much all VB topics as related to coding standards.I've been programming in VB for many years, so much of this was not new to me, but it did have some helpful tips. His chapter on comments is very good and had some helpful insight for writing better comments.The last chapter covers how to set up Visual Source Safe, a topic that I was interested to see included here. It is somewhat unrelated, but it is in fact a very useful step-by-step guide to setting up this tool for source code control. This alone makes this book worthwhile if you're not using VSS now and would like to.
Practical Standards for Microsoft Visual Basic
A very well written book about what you should have learned in college (or your first programming class in high school). If you program for a living you should be applying these concepts already, but if you slept through your software design classes then definatly read this!I don't like the authors frequent use of the goto statement, and I'm not a big fan of Hungarian notation but those are the only two negitives I find (and hence the reason for 4 stars). He does an exceptional job of showing both the wrong way and the right way to accomplish the topic he is covering (for instance having only 1 exit in a sub)..Well worth the read.. matter of fact I'm going to be suggesting this to the project managers at work as a "must read" for new hires and veterans alike.
Practical Standards for Microsoft Visual Basic
I have read countless VB articles, and books, and have often longed for a one-stop resource about structured VB programming. When working with different teams over different periods of time, I have often found that little or no standards are in place. Consequently, the time to get a feel for someone else's code can sometimes be more than the time to fix it.Foxall's book isn't an end all to programming in VB. And some may feel that he is telling you how to code, and stifiling what many programmers fear-their individuality. This simply isn't the case. Foxall breaks down all the aspects of a VB project, and how to best document, declare, write, and design your code.This is the most practical book I have ever read. Thanks for a wonderful book. And more thanks for something that's equally as practical.
Practical Standards for Microsoft Visual Basic
Foxall's work is valuable not only for what it encourages and discourages with clear, persuasive examples of good versus poor VB programming practices, but also for the compelling way in which he unifies the underlying principles of his thinking into an elegant advocacy of extensible, maintainable code.This book belongs in every VB team leader's right-hand desk [email protected]
Practical Standards for Microsoft Visual Basic
Many VB developers are used to writing the code anyway they please, however, when you or anyone else needs to debug your applications couple of weeks later, it's harder to understand what is going on in the code unless you follow some standards. This book tells you what standards you should follow, offers examples, explanations, and reasons.Get it, because you will learn something, regardless of the version of VB you are currently using.
Practical Standards for Microsoft Visual Basic
There are some books you wish every VB programmer would read, this is one of them. I used this book as a helpful reference to develop programming standards for two developer groups. I did not agree with all the standards in the book. I felt that some of them were not actually the standards followed in the industry, but most were well laid out and if followed would improve the VB programming industry.Some areas were covered more indepth than others and those that were not covered so well probably should have just been left out. (Source Safe, Error Handling [get an error handling book])All-in-all a very good book and I don't believe there is a better VB standards book on the market today.