Archive for August, 2010
Recently Eric Schmidt (CEO of Google) talked about the “Dark Side of Social Networking“. His view is one day people will change their names in order to escape the online persona they have created and he is right except that “one day” is really today.
Many companies are now checking Facebook, Twitter, etc. as part of the hiring process. Even at my job Facebook and MySpace is checked on potential hires.
So here are some things to think about when you create or post on social networking sites:
Posts Are Archived Somewhere
Recently the Library of Congress has started archiving all twitter tweets. This means that anything you say (at least on twitter) is accessible in perpetuity. So don’t post it unless you mean it.
Potential For Misuse
If I am the leader of a cult, a government radical, or if I have an alternate sexual lifestyle how does that affect me getting hired to an office job? I am none of those of course, but I just pose the question. Could they just pass your resume over if they see something online they don’t like and that you didn’t list on your resume? I bet this happens more often than not.
This kind of ties into the misuse section but there is a saying on the internet. It’s called “Rule 34″ and it says that if it exists then there is porn of it. I wonder how many potential hires and employees there are out there that this holds true. How do you think nude pictures of yourself work for getting that job? Even if you get or have the job how serious is anyone going to take you after seeing the photos?
The answer to this one is just don’t post photos of yourself in embarrassing or compromising positions even if you think it’s a non-public area (facebook can and does get hacked). If you do have them on your PC get rid of them and/or don’t give them to anyone. This includes boyfriends/girlfriends. Nothing speaks revenge more than posting your nudes all over the place after a bad breakup.
Creating Another Account
Within the last year my job has opened up twitter to some of the I.T. staff including myself. The benefits of this I have posted a few months ago in “No I.T. training budget. Twitter to the Rescue!“.
However, due to the fact that I sometimes like to post NSFW jokes, family communication, family photos, and other non-work related items I created another Twitter account for personal use outside of work (@greeleygeek for work, @amidageek for personal).
In my view using my personal account now is no different than text messaging or making personal calls at work. Even this blog falls outside of the scope “work-related” in some posts, which is why I post on evenings and weekends.
Doing this has safeguarded any problems with posting questionable content at work and has effectively separated my “work online persona” and my “personal online persona”.
Be Careful What You Post At Work
You must be careful of the data you post because of trade secrets, private work information, etc. I see this becoming more and more of a concern of employers to monitor these areas and also many more people getting fired for sharing something they weren’t supposed to.
Too Much Information
Another danger is too much information. One of our friends has a teenage daughter that regularly posts her location on Facebook. “Home alone again. Popping some popcorn” may seem innocent, but a savvy internet stalker would have that address and be on their way. This is a why I suggest that you don’t share your location unless you want people to find you.
- Watch and think carefully about what you post on work time and/or accounts
- Create a second account if you want to post personal items (non-work related) and post after work hours.
- Do not post your location if you don’t want strangers to find you
- Do not post incriminating photos of yourself online. They will be seen.
- Remember. What you post could affect current and potential opportunities.
To wrap up here are some links of people getting busted breaking the above rules:
Guy calls in sick, but posts he’s hung-over on Facebook
Woman posts on Facebook by accident (NSFW)
How twitter can get you fired in 140 characters
Woman stalked on Facebook by ex-boyfriends other lovers
Share and Enjoy
Yesterday morning I attended Sharepoint Saturday down in Denver.
From the Sharepoint Saturday website (http://sharepointsaturday.org):
“SharePoint Saturday is an educational, informative & lively day filled with sessions from respected SharePoint professionals & MVPs, covering a wide variety of SharePoint-orientated topics. SharePoint Saturday is FREE, open to the public and is your local chance to immerse yourself in SharePoint! ”
The first session I attended was “Upgrading Your Custom Developed Solution from Sharepoint 2007 to Sharepoint 2010″ by Shai Petel (from KWizCom – http://kwizcom.blogspot.com/).
The biggest takeaway from this session were the new Sandboxing features of Sharepoint 2010. This allows you to deploy a solution in a sandbox and not bring down the entire Sharepoint collection if your solution has bugs/memory leaks (a problem with previous versions).
Next up was “Caching-In for SharePoint Performance” by Sean McDonough (http://sharepointinterface.com/). My takeaway here was with SharePoint caching the key element is balancing the type of users. The more unique the users the more things like page output caching for SharePoint might not work well for you. He also covered BLOB caching and Office web application caching. A very interesting and informative session.
Lunch – super excellent spread and tons of vendors were there. Lots of swag.
After lunch I attended “Covering your behind – SQL Server and high availability and SharePoint” with Art Laubach. This probably was the least informative as it covered Mirroring and Clustering (two topics which, being a SQL MCITP, I already am well versed in). However, it was good to know that SharePoint does perfectly fine for both which was something I have not researched up until this point.
“Introduction to Sharepoint applications using InfoPath and Forms Services 2010″ with Darvish Shadravan (Microsoft) was an interesting look at the new features of InfoPath and Sharepoint 2010. However most of the cool features like integrating the Office web application features was Enterprise version specific. However these features would be nice as anytime we need a form we have to develop an ASP.NET solution. This isn’t so much of a problem but with SharePoint we could have the versioning built-in rather than resort to Subversion or other versioning system.
The last session of the day ended with “Best Practices for Content Lifecycle Management with Microsoft SharePoint” by the SharePoint guru Mary Leigh Mackie from AvePoint. This was an excellent walk-through of strategies to manage content and scale out your SharePoint installation covering topics such as Remote Blob Storage in SQL (this may be a future blog post), and training end-users.
All in all this was a great experience and well worth the Saturday. SharePoint MVPs were on hand to answer questions and Gary Lapointe (http://stsadm.blogspot.com) even donated two MSDN licenses at the final give-away.
Needless to say I am excited to get back to work with a new outlook on SharePoint and am already looking foward to next year.
Share and Enjoy