Tech versus non-tech terms

There are times that when you are listening to a group of people have a discussion you may think that they are talking a foreign language, but they are speaking English, just that they are using terms that don’t seem to make sense in the conversation. In some of these cases, it isn’t the word or term that they are using, it’s how it is understood by everyone that is part of the conversation. I do know that a lot of technical people have what seems to be a secret language that they speak, and it can be very confusion for those that are not directly related to a particular expertise.

I have decided to try and decode some of the words that I have been hearing and how they can be misunderstood by those around us. Now let’s have some fun and see how one acronym or term can mean a lot of different things, and it all depends on who is listening to the conversation.

DC

• Direct current
• District of Columbia
• Domain controller
• Data centre

Backup

• Extra help or support
• Copy of a file
• A situation in which something is not moving
• Music that accompanies the main singer or tune

SAN

• Storage Area Network
• SANS institute

Farm

• A plot of land that grows crops and livestock
• A group of computer systems in one or more cabinets.

These are just four examples of how a word or acronym can have more than one meaning and when you are in a conversation with a bunch of people it can be very confusing to listen to a conversation. One important thing to remember is when you are writing an email, or a document, and you use any of these terms it is important to ensure that everyone that may read the email or document understands the correct meaning of the term. Be careful of prejudging what "Everyone" knows.

It is very important to know the audience that you are writing something because even if they are in a different area of Technology, they may have an entirely different meaning for the same term. So, a term can have a lot of different meanings, and understanding how to communicate to the various people in an organization is very important. It is the translating infosec into regular IT and IT into regular business terms that is vital for good communication.

Rebooting and why I should do it

For many, having to reboot/restarting our computers seems to be such an issue. Why can’t I just leave it turned on for days at a time and even connected to the company for hours and days without anyone complaining.

Here are some of the reasons why we all need to reboot/restart our computers/device:

• A full shut-down restart/reboot is required for completing many of the security patches needed to keep your (personal, corporate, and family) data and reputation safe.
• A restart refreshes your system of the many "temporary" processes that have done their job, but haven't fully release system resources

We have been working with a client and when we talk to them about getting the end users to reboot/restart their devices it seems to be such a challenge. Of course, there are so many reasons why someone cannot reboot their system on a timely basis:

• I have files open that I need to keep open because I am working on the files (these files are open for hours even when the person isn’t working).
• My system takes too long to reboot when I do a restart (maybe the issue is you haven’t done restarts lately and there are too many things that need to be updated).
• I just don’t have time to do a restart (why not restart your computer at the end of the day, and it will ready when you get back the next business day).

There are so many reasons why someone will tell you that they cannot reboot/restart their system, and a lot of those reasons are that they just can’t be bothered or there isn’t a reason for them to reboot. In some cases, the reason someone isn’t rebooting/restarting their device in a timely manner is because there is no policy in place that says that all devices must be restarted with x number of days. When a business doesn’t have a policy as to how often machines need to be rebooted/restarted, that doesn’t help at all.

For a business to be successful and secure, they need to understand the importance of restarting/rebooting each machine is vital. Some users think that either putting their device into hibernation mood/sleep or a system crash means that a computer has rebooted, has completed the task. What people don’t understand is a crash doesn’t mean a total system restart, and putting a computer into hibernation is not a restart.  For a device to work effectively, they need to have regular, total reboot/restarts. It doesn’t matter if it is a computer or tablet, they all need that bit of time when they can turn off and restart to clear all the stuff that has been bothering/hindering them.

It is important that we understand that our devices, either a computer or tablet, need a bit of time when they can turn off and refresh. So, yes, it is important that we remember that our devices need a bit of time to sleep, even if it is just for a couple of minutes. It helps them recharge and know that they are ready to go and meet your needs again.