While this probably applies more to a significant part of my line of work and others that do coding and/or scripting this can be applied generally to any other sort of data, content or programmatic creation.
SQL or Server Query Language is what I use to import, manipulate, interpret and extract data from databases almost every day at work. Sometimes, the queries are fairly simple spanning just three lines:
SELECT *
FROM database
WHERE column = ‘value’
Otherwise, some queries can be tens of rows or even more depending on the level of summarisation and derivation required with the data that I have available. Some of the trickier ones can take hours to craft to ensure accuracy, speed and scalability after careful thought and consideration.
Unfortunately for me, there is no autorecover for the scripts that I write unlike Microsoft Office applications but even then the autorecover functionality should not be relied upon as your backup. Therefore, I need to save and save often – saving takes little time to do and saves a huge amount of hassle and it also gives you an opportunity to compare how different revisions of your work in case the results are not as you expected or you have a great bit of code elsewhere that you want to drop into your latest creation.
Follow Us!