Tag Archives: reliability

Not like you didn’t know this but, another story of Twitter’s slow demise…

logoI got wind of a story about twitter today while I was viewing some articles in my google reader (da bomb btw). The story stated that the company Pingdom.com has been monitoring the up-time of social networking sites. Well it should come to no one’s surprise that Twitter.com is the worst out of all the sites listed. The downtime is to the tune of about 37 hours so far this year. The stats have only been recorded since January 2008. As I keep saying Twitter needs to get on the ball and fix the issues at hand cause we the users are feed up at the spotty sometimes unreliable stability of the system. I mean we are already subjected to 140 characters to say what we are doing, just make sure I can post when I want to please powers that be…. Someone at Twitter has to take the position of “Yes…I give a damn” and fix the issues, and while I’m talking about that, can the people who make changes to twitter stop doing things over the weekend that affect my usability. Maybe a couple of apple engineers from the UI department can help us with a better pleasing interface that does not change on a whim. One day I know they will get it right I just hope that happens before we start jumping ship….Please for the love of (Politically correct) who ever you think is the higher power in your life, not letting the other powers that people can thank of down.

TBTR

Twitter is always slow, could Ruby on Rails be the culprit or Management?

RoRTwitter

I ran across an article on Crankygeeks.com about Ruby on Rails. Warning this post might get a bit technical and thus not really interest you, but hear me out for a moment. I heard about ruby on rails, oh 2 or so years ago. Just like some of the other programming languages it has it’s good and bad points. Some would say it takes less time to code in RoR but others would argue your sacrificing something. If you have ever run code, or created code you know the computer systems have a hand in the speed. Sometimes people create code on the slowest computers and never try to upgrade the systems for lack of money, bloated code, or lack of expertise. As many of you know that Twitter has been very slow at times and while that is a burden when your trying to follow a conversation it also gives you a hint to get back to work instead of killing your productivity.

The twitter team

A week or so ago I saw a post from someone saying that a key employee at twitter was fired (The Guy on the Far Left) and no longer working with them. As my understanding this guy had been brought in to help with the spotty and unreliability of twitter in the past few months. To know the guy got fired was a bit dis-hearting to say the least, I mean I didn’t know the guy but for someone who was bought in at the beginning of the year and to be fired already says a lot to me. (btw his twitter account still works)

Twitter sucks as a company has the potential to be a great company and while I don’t live in San Francisco or California for that matter. I wonder if management is jumping to conclusion already about there new hires? Its plain to see that if you hire someone in January and fire them in March or April something didn’t mesh. It could have been a culture shock for both employee and employer but what ever the case. When someone is fired fairly fast it means something just ain’t right. I hope that twitter get a hold of the reigns it seems money is starting to talk and starts to pull in the issues they have on their plate at this time. If management does not get a hold of the issue at hand when the next darling comes along we will all jump ship. Don’t doubt that people won’t jump, look at the Lifecasting relm justin.tv, ustream, and others we jumped for features and reliability this could definitely happen to twitter if the parts don’t start to assemble properly.

Conclusion Ruby on Rails is great…RoR+Twitter=jury still out…twitter management might just need an enema before they lost traction.

Just my two cents (with run on sentences, misspellings, incorrect punctuation, and procrastination laced)

TBTR