Skip to main content

Wake Me Up

Last week, I was driving to and from various meetings with the business news on the radio when I heard the story that Facebook had some secret "thing" to announce to the media.  Perhaps I'm jaded but I immediately recognized this as an attempt to emulate the mastery that Steve Jobs had regarding his relationship with the media, so I was curious but thought little more than that.

As you all know, the announcement really wasn't that exciting after all.  The concept behind Friend Search (not the official name, but one that sounds better than the official name: Graph Search) is a decent one.  But the main problem I have with it is that most people aren't using Facebook for posting information that is worth searching through for answers to your problems.  David Hersh phrased it very nicely in my interview with him in 2010:

"Rather than continuing down the path of becoming a place to share meaningful content with 'real' friends, the focus on status updates flowing through the news feed has, in my opinion, shifted the focus squarely from utility to entertainment."

A lot of professionals that I know avoid mixing work with Facebook because of the huge potential it has to be detrimental to their career.  Granted, simply behaving like adults would mitigate much of that risk. But until the Federal courts decide that demands by a potential employer for your login credentials is an invasion of privacy (especially if your Facebook content is viewable by a restricted audience since information that is available to the general public cancels a person's ability to claim privileges to the privacy of that information) the number of professionals hawking their talents on Facebook will be minimal relative to the total user base.

What we're left with to sift through for answers to life's most challenging problems is your friends' postings about their kid's day at school; links to music or other videos; or images that exist solely to display the text of some witty saying that isn't searchable in the first place because it's an image.  And I'm supposed to be able to solve world hunger via a lolcat?

It should be obvious that I considered this announcement to be a rather boring affair, and it isn't the first time that Facebook has let me down.  Would you pay them to allow a message to reach someone's Inbox?  "Not I," said the pig.  And it is my guess that the moment this feature is enabled and people like me start receiving spam from telemarketers, there will be a rather substantial exodus to other social media websites.  Maybe Instagram will finally get those users back who defected after they attempted to change their Terms of Service, eh?

Edit:  maybe that defection has already begun, according to an article in the WSJ.

All of this reminds me of the smart phone commercial where Apple is ridiculed as causing mind-blowing experiences simply because they moved the headphone jack to the bottom of the phone.  Since there is some truth to that commercial, perhaps Facebook is more closely emulating Apple than I first thought.

Disclaimer:  I have an iPod Touch, iPhone, and iPad.

When Facebook productizes their platform so that corporations can use it internally a la Chatter then I'll find reason to rejoice.  I realize they aren't doing too badly from a financial perspective (ignoring, for the moment, the overhyped IPO and its impact on the stock price because they weren't literally printing their own money like many of those who bought those shares seemed, incredulously, to believe), but I can't help but wonder if the person steering the ship from a strategy perspective really is clueless on how to tap into the enormous potential this company has from a revenue generation perspective.  The answer to that, however, won't be known until the first anniversary of its IPO date (and subsequent release of the 10-K along with comments by the executive management team on future directions for the company).

Or maybe someone will take a break from posting their latest Paleo diet recipe to write the answer to that question on their wall so that I can find it with Friend Search.

Popular posts from this blog

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...