Realized Solutions is more than just a Managed Service Provider (MSP), RSI proudly designs custom software for their clients. One of the many tools RSI uses with the software development is something called “Scripting”. Scripting can take on many different meanings but our focus in this article is on Scripting languages and Ad-Hoc Scripts, both vital to software development in today’s world.
Scripting Languages
Scripting languages such as JavaScript, PHP, Python typically are the first thing developers think of when the word Scripting is used. Scripting languages are programming languages run by an interpreter, translating the code to machine code at runtime. By far the most common scripting language is JavaScript. All modern browsers each have their own interpreter to read JavaScript Scripts to give webpages that robust and interactive feel we see in modern websites. Every time we click a button or scroll through a webpage, scripts are triggered to give the desired popup, sound, or movement on the page. These scripting languages (Server-Side Scripting) can be used for backend work, using backend interpreters to run scripts when events from the front end are triggered.
Pros vs. Cons of Scripting Language
Scripting languages are great for lightweight applications where heavy processing is not a factor. They can be quick to develop because of their easy-to-understand syntax and they do not need to be compiled to run. This is why many startups use Scripting languages when starting out, to get a performant application out fast. However, because scripting languages are interpreted at runtime, this can sometimes cause mediocre performance under heavy load. This is why bigger and established companies typically use Compiled Languages such as C/C++, C#/.NET or Java.
Ad-Hoc Scripts
No matter what field you work in, whether it is development, carpentry, or accounting, we all use tools to speed up tasks and boost productivity. Some of these tools are created by professionals themselves.
For example: a Carpenter may make a template to attach cabinet hardware to dozens of drawers and doors. Developers use Ad-Hoc scripting to automate tedious tasks and Ad-Hoc scripts come in all shapes and sizes.
At RSI we use PowerShell, SQL and even C# to create efficient scripts which are fast and accurate vs. the slow redundant time-consuming tasks people may be used to.
A recent example RSI used was a combination of PowerShell and SQL to create an Ad-Hoc script to automate the process of restoring test environments. By using this method, a task went from a thirty-minute process down to five minutes.
Pros and Cons of Ad-Hoc Scripts
When considering the example from above, the Pros are very appealing with one script boosting productivity by 600% and ensures the restore process is accurate and mistakes aren’t made. Speed and accuracy is our #1 focus, and when used correctly the Cons are minimal and the time spent is to write the actual script. However, using Ad-Hoc scripts to make changes to data can be problematic. Most data found in databases are placed there by logic in code that has validations, which means it controls and organizes the data. Scripts circumvent this validation, and if done incorrectly this could lead to bad data, which in turn could cause your program to fail. When looking at any option, RSI takes the decision very seriously and reviews every option very carefully for the best outcome of their client(s).
