Toluu

Dare Obasanjo aka Carnage4Life

You can buy cars but you can't buy respect in the 'hood - Curtis Jackson

Lessons from Google Wave and REST vs. SOAP: Fighting Complexity of our own ChoosingAugust 27

Software companies love hiring people that like solving hard technical problems. On the surface this seems like a good idea, unfortunately it can lead to situations where you have people building a product where they focus more on the interesting technical challenges they can solve as opposed to whether their product is actually solving problems for their customers.

I started being reminded of this after reading an answer to a question on Quora about the difference between working at Google versus Facebook where Edmond Lau David Braginsky wrote

Culture:
Google is like grad-school. People value working on hard problems, and doing them right. Things are pretty polished, the code is usually solid, and the systems are designed for scale from the very beginning. There are many experts around and review processes set up for systems designs.

Facebook is more like undergrad. Something needs to be done, and people do it. Most of the time they don't read the literature on the subject, or consult experts about the "right way" to do it, they just sit down, write the code, and make things work. Sometimes the way they do it is naive, and a lot of time it may cause bugs or break as it goes into production. And when that happens, they fix their problems, replace bottlenecks with scalable components,

Google Wave and Network EffectsAugust 5

This morning I stumbled on a great post by Dave Winer titled Why didn't Google Wave boot up? where he writes

So why didn't Google Wave happen?

Here's the problem -- when I signed on to Wave, I didn't see anything interesting. It was up to me, the user, to figure out how to sell it. But I didn't understand what it was, or what its capabilities were, and I was busy, always. Even so I would have put the time in if it looked interesting, but it didn't. 

However, it had another problem. Even if there were incentives to put time into it, and even if I understood how it worked or even what it did, it still wouldn't have booted up because of the invite-only thing. It's the same problem every Twitter-would-be or Facebook-like thing has. My friends aren't here, so who do I communicate with? But with Wave it was e

There will be many social graphsAugust 2

I've spent the past week going over the ideas in Chris Dixon's excellent post titled graphs and thought the ideas were powerful enough that they are worth reiterating. The thesis is simple, in recent years many have been focused on social graphs (i.e. graphs bidirectional or one-way “friend” relationships between users) but there are other ways in which users can be connected to each other besides whether they are friends or not. The key points from Chris’s post are excerpted below

Facebook’s social graph is symmetric (if I am friends with you then you are friends with me) but not transitive (I can be friends with you without being friends with your friend).  You could say friendship is probabilistically transitive in the sense that I am more likely to like someone who is a friend’s friend then I am a user chosen at random. This is basis of Facebook’s friend recommendations.

Twitter’s graph is probably best thought of as an interest graph. One of Twitter’s central innovations was to discard symmetry: you can follow someone without them following you. This allowed Twitter to evolve into an extremely useful publishing platform, replacing RSS for many people. The Twitter graph isn’t transitive but one of its most powerful uses is retweeting, which gives the Twitter graph what might be calle

Change is bad. No, change is good. No, change is bad unless it’s greatJuly 29

One of the challenging things about working on large scale services that lots of people use every day is that they get attached to their experience with the site and enjoy the familiarity. A consequence of this is that there is a large population of users for whom any change whether good or bad is met with resistance. 

One of the things that you end up learning when building a product is that if you’re afraid that a lot of people may complain about the changes you’ve made to the product they use every day then you’ll end up never making any changes.

Now Playing: 50 Cent -

Some Thoughts on QuoraJuly 15

I was reading Pandas and Lobsters: Why Google Cannot Build Social Applications... and came across the following statements

Now, consider the Four Horsemen of Hotness in 2010: Facebook, Quora, Foursquare, and Twitter. Think deeply about why none of these four could have been developed inside Google.
...
Quora is restaurant that serves huge quantities of bacn and toast. Quora is a dozen people running dozens of experiments in how to optimally use bacn to get people to return to Quora, and how to use toast to keep them there. Bacn is email you want but not right now, and Quora has 40 flavors of it that you can order. Quora's main use of Bacn is to sizzle with something delicious (a new answer to a question you follow, a new Facebook friend has been caught in the Quora lobster trap, etc.) to entice you to come back to Quora. Then, once you're there, the toast starts popping. Quora shifts the content to things you care about and hides things you don't care about in real-time, and subtly pops up notifications while you're playing, to entice you to keep sticking around and