One guideline every VB.NET project should follow!

I have been playing video games since mid-90's, when Windows 95 came out. I was around seven years old at the time. One thing led to another and I was exposed to some (scripting) languages including VB4, PHP, HTML and CSS.
It was not until summer 2010, after a Bachelor Common Art and Cultural Sciences and a Master Media and Journalism, that I decided to become a professional programmer. I was hired by a company and they taught me the basics of VB.NET and WinForms and using SQL Server database.
At the end of that same year I signed up on CodeProject and that is when my programming knowledge increased rapidly. Being around some of the best and most enthausiastic coders in the world certainly helps you develop your own skills. I learned various Object Oriented Principles such as SOLID and Design Patterns.
I am still working in VB and WinForms using DevExpress Controls and the .NET Framework 4.0. I have experience in ADO.NET, Entity Framework 4.0, LINQ, TPL, WCF, and SQL.
I have also written some articles[^] for CodeProject in both VB and C#. My second article, What not to do: Anti-Patterns and the Solutions[^] became best VB article of the month april 2011, of which I am very proud
For those wondering what happened to my Bachelor Common Cultural Art and Sciences and Master Media and Journalism, I currently hold an MA title in Media and Journalism. I am not really doing anything with it, but I guess it helps me write those articles