Skip to main content

Balmer Doesn't Get Social Networking...Few People Do

Web 2.0 is about community. Web 2.0 is about relationships. Web 2.0 is NOT about Ruby on Rails. Web 2.0 is NOT about building a "better" MySpace.

Robert Scoble posted an interesting tirade yesterday about Steve Balmer misinterpreting social networking. Scoble cites Balmer's propensity to respond with the Microsoft insular comment about Web 2.0 "We could build [fill in the blank with Web 2.0 technology] in a matter of [short period of time]" as wildly off base. I couldn't agree more.

Scoble's most compelling argument focuses on Ebay. Ebay isn't successful because of its technology. It's successful because it surpassed the tipping point. Everyone uses it for auctions. Why would I want to use another service to buy or sell something when everyone is on Ebay?

Every time I see a job-board listing needing a Ruby/PHP/whatever developer to "build a Facebook-like" application or a "Monster-like job board", I cringe. So some engaging entrepreneur has orchestrated a way to build a better mouse-trap. So what? You're wasting your time and money.

Of course you could build a better [fill in the blank with Web 2.0 technology] given adequate resources--but it doesn't matter because the social network has already formed around Ebay, Facebook, MySpace, LinkedIn, YouTube, etc. Have you looked at Craig's List lately? It's difficult to look at it's so ugly...and yet, it's the destination for local people-centric, one-time commerce.

So, my advice to you aspiring entrepreneurs: innovate horizontally; not vertically. Come up with the next social or community offering--don't simply repeat what's already there but with a better [interface|design|API|etc]. Can you say Ubid.com? 'Nuf said.

Comments

Unknown said…
That said, if you provide some real tangible difference, your new company does have a chance. It is slight, but it is there.

By the logic above, Google should have never bothered since Yahoo owned the search market.

The problem is that the "me too" business model doesn't work on the net. For those gen xers out there, think of it like this. Why on earth would you play with go-bots when there are transformers right there for you to play with.

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)]

I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent!

I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around.

Thanks in advance!

Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario...
I'm workin…

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error:
"TF30042: The database is full. Contact your Team Foundation Server administrator."Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file.

Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve:

Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here.
Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. The Auto_…