Same story, different month 3 years ago

Its like you can only pose for so many front-page exposes on your company before you have to start doing some work.  My favorite was when <a href=”http://twitter.com/ev”>ev</a> was talking about how we’ve been spending the past few months building new features for Twitter.  Ha!  I love it.  <strong>Writing</strong> features?!  Fuck that.  We’re taking features away my silly little friends.

Which brings us to the last week or so.  You know, we could get up here and tell you that our SMS aggregator isn’t working so many times before you guys figure it out.  Because let’s be honest; SMS is <strong>not</strong> hard.  The reality is we’re bleeding cash and we figured it would make sense to just sort of randomly drop 40% of our SMS messages on the floor.  Its like roulette now.  Only better!!  Now, we’re the geniuses for cutting costs by a full 15% (yeah, you do the math suckers) and we have the means to wratchet that up or down.  Its just you silly users that suffer.

And then there’s this morning.  “Database upgrade”.  Haha.  OMG.  Who comes up with this shit?!  Oh wait, we do.  Ha!  Because that makes sense.  Let’s do an upgrade on a Tuesday morning PST.  Totally makes sense.  Retards.

Here’s the deal; as you all know Twitter is a <strong>really</strong, really hard problem.  Like harder than porn.  I mean seriously.  140 chars to like almost a million people?!  Yeah.  Think about it.  <strong>1 million</strong> people.

The database is fine; we’re just waiting for our sysadmins to get in (they usually get in at 10:30am or so - its the Valley baby) to “reset” the servers.  In the mean time its motherfuckin’ mimosa’s and Krispy Kremes.