Finally on Yelp

I finally signed up at Yelp.  Here’s my profile.  The plan is to write reviews for as many places in Seattle and Los Angeles as I can think of, time permitting of course, then to write a review for each place I visit in San Francisco.

Also notice my little sidebar widget for my recent reviews; pretty shnazzy I would say.

Tech Marketers, Meet Your Maker

I’ve been meaning to write a post about the comedic potential of listening to non-technical marketers talk about technology.  I’m only referring to the marketers who speak with such conviction that innocent bystandards might actually believe they know what they’re talking about.  I’ve witnessed this many a time when speaking with MBA-types about various web startups.  I would normally cite specific examples, but Larry Ellison, CEO of Oracle, has done better than I could ever do.  Read this short article about cloud computing and silly marketers who want so badly to be technical but fail miserably.  It’s like a new Revenge of the Nerds, even though Ellison probably isn’t a nerd given how much cash he’s rolling around in.

What’s curious is that the title of this post is “Larry Ellison’s Brilliant Anti-Cloud Computing Rant.”  That’s completely misguiding.  This isn’t an anti-cloud computing rant; it’s an anti-marketer-who-speaks-with-conviction rant.

Twitter: A Case Study for Bad Software Development

I read (yet) another post about Twitter’s performance problems, but this one unlike others shined light onto the technical difficulties that Twitter is facing. From the post it appears as though Twitter was created too rapidly with an underemphasis on performance. It’s very easy for software developers to be so interested in cranking out features that they disregard performance altogether. I think Twitter is one of these cases. Read the post for more details, but basically they were naive when developing their application and didn’t dig deep into performance bottlenecks and limitations.

Let this be a lesson that performance must be a factor when developing an application. Consider what will happen to your code if you experience an insane amount of usage, and understand the performance bottlenecks that you’ll have. Google is a good counterexample to Twitter. Larry and Sergey knew how difficult it would be to create a fast index of the internet, so they developed tools to deal with large data. I’ll bet the developers at Twitter are running around like maniacs, profiling, testing, and screaming profanities. Had they taken performance into account earlier they could have avoided their recent downtime altogether or at least been more prepared to fix the problem when it occurred.