Skip to main content

Google Plus exposes the Achilles Heel of Facebook


Last week I’ve got an invite to Google plus last week (thanks @iein) and had a chance to play around with it.  We have gone through many waves of social networks. Friendster, Orkut, MySpace and every new social graph addressed a major annoyance of the previous one.

I used Friendster and Orkut for a bit, but both of those didn’t catch people’s attention enough to keep them sharing information every day. MySpace saw real mass adoption but it completely failed with its design. I remember being frustrated with people’s pages, the auto playing videos, bulletins that were over run by club promoters and the rest of cheap design. Then came Facebook and it addressed some of the things that MySpace refused to fix.

For me Facebook was a big winner because you had to prove your affiliation to a certain college. You also didn’t have crazy designs on people pages. You didn’t have limitations on pictures and you had the news feed. MySpace reacted to those features way too late and it was probably afraid that it was going to lose some of its users if it became more strict and less customizable.

Now we are seeing people’s frustration with Facebook. The number one frustration is privacy. If you let people into your network they are free to see everything. If you don’t then they feel like you don’t want to associate with them.

People have gone around this issue by creating several profiles. Some just stopped sharing personal information altogether. Facebook has continuously erred on the side of overexposure of your data. Overexposure of your personal life is what kept people who are in your circle coming back therefor Facebook had no reason to fix it.

Google Plus holds a promise to fix the oversharing mess. Alexia’s Tsotsis’ article describes the difference between Facebook social networking and real world social networking. Facebook better react quickly or soon I will only share my personal info only on the network that promises to keep it to my inner circle of trust. 

Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…