VBScript best practices

by Jeremy Saunders on December 6, 2008

If you can’t tell by now, I love scripting and coding 🙂 There is nothing you can’t achieve, and no problem that cannot be resolved. But there is an art to doing it right. I start by drawing up an N-S (Nassi-Shneiderman) diagram or flow chart, and then writing it up in pseudocode, which allows me to focus on the logic of the program without being distracted by details of language syntax. I choose to write VBScript because then it can then be maintained by colleagues and customers. Although now I’m starting to get into PowerShell, which is fast becoming the defacto standard. When I write a script I try and abide by several golden rules. Rob Haupt has explained them perfectly in his blog titled My five VBScript ‘best practices’. I believe that there is no point doing things half hearted. So do it properly or don’t do it at all!

Jeremy Saunders

Jeremy Saunders

Technical Architect | DevOps Evangelist | Software Developer | Microsoft, NVIDIA, Citrix and Desktop Virtualisation (VDI) Specialist/Expert | Rapper | Improvisor | Comedian | Property Investor | Kayaking enthusiast at J House Consulting
Jeremy Saunders is the Problem Terminator. He is a highly respected IT Professional with over 35 years’ experience in the industry. Using his exceptional design and problem solving skills with precise methodologies applied at both technical and business levels he is always focused on achieving the best business outcomes. He worked as an independent consultant until September 2017, when he took up a full time role at BHP, one of the largest and most innovative global mining companies. With a diverse skill set, high ethical standards, and attention to detail, coupled with a friendly nature and great sense of humour, Jeremy aligns to industry and vendor best practices, which puts him amongst the leaders of his field. He is intensely passionate about solving technology problems for his organisation, their customers and the tech community, to improve the user experience, reliability and operational support. Views and IP shared on this site belong to Jeremy.
Jeremy Saunders
Jeremy Saunders

Previous post:

Next post: