Tag: support

Finding a balance for sharing

Social media is helpful in many ways, but one of the dangers I think is the risk of oversharing. I think finding a balance for sharing is very important.

There are many reasons why oversharing is harmful both to the person sharing and those who read.

  1. You may be turned down for a loan. Banks and other financial organizations are looking at your social media account to learn about your personality. Why? One of the 3 C’s as we were told is character, and they want to see if not only you are responsible, but your friends are responsible. The theory is that if you have a friend who doesn’t pay a bill, you might be the same and the risk of lending to you in increased.
  2. There is no forget button. Whatever you share is forever on the Internet. It doesn’t matter if you delete the post, it will surely get archived and copied. You may feel good about something you share at the moment, but the future may have a different perspective on it. If you aren’t sure if you should share something, then don’t.
  3. Your words will come back to haunt you. I shared something once with the FCC when they sought public opinion on a decision they made. Ten years later when I googled my name it came to the top of the list. It wasn’t something that the FCC said they would share, but once I published it, it was out of my control. You should assume that anything you write on the Internet is public and part of the record forever.
  4. Your words can be used to harm others. You may write something with the intention of positive results, but as I said before positive intentions aren’t enough. There are tons of positive intentioned and ignorant people on the Internet. I try to write things that are supported by mainstream science, and not on any crazy fringe groups. However too often science discovers something new, and when that happens your advice is no longer accurate. So if you want to stand by your words, you need to constantly evaluate them with the new information that comes out daily and revise them when appropriate. Sadly 99% of people do not update their writing, so most information on the Internet is quickly outdated.

How do I manage these problems with what I write? I review things that I write everyday as part of the work of having this blog. I go through and try to delete articles that are no longer true or things that have a low interest by others. I always encourage the reader to challenge what I say, and the greatest compliment to me would be “I don’t agree with you, but it made me think.”

Everything in life has a balance, including sharing.

Stories from My Past: Be careful what you ask for

In IT you often find that when you give people exactly what they want, they are sorry they ever asked.

I helped one person who wanted a new version of Adobe rolled out to the entire company. They were working on a project and that project needed a new version of Adobe. Not an unreasonable request. I asked someone to test that new version and they tested it.

A week later that person had a different problem and I went to help them. It turns out that the fix was to upgrade their version of Adobe just like the other person who was testing it. However when I went to upgrade them they said “Maybe we shouldn’t upgrade this because it might break my other applications.” This was the same person who asked for the entire company to be upgraded the week before. I agreed that could happen, and upgraded him anyway. It worked fine. Problem solved.

Of course I went to my supervisor and told him what happened. The same person wanted the entire company to be upgraded, but not himself personally. You can’t have it both ways.

Often the quick and easy answer seems to be upgrading the software. Many times this is the correct one. I personally like using recent and supported software. However not every company believes in this. Many companies use very old software that is poorly supported or not at all. This is the main cause why they have problems as well.

To me, when you quickly want to make a major change and don’t consider the consequences you are just asking for problems. If I had upgraded everyone that day like it was my technical ability to do, I might have unleashed worse problems. Having someone test a change is so helpful, and so basic in giving the best IT experience for users.

If you want disaster make a quick change. If you want stability, think decisions through.

Related Post