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!

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …