Comments on: Five Things Twitter Shouldn’t Be Doing http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/ The Blog Of Andrew Dobrow Sat, 11 Oct 2008 19:55:53 +0000 http://wordpress.org/?v=2.2.1 By: To Tweet or to Friendfeed http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-136 To Tweet or to Friendfeed Mon, 26 May 2008 22:03:02 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-136 [...] ben alvast niet één van die voorstanders (zoals Scoble) om Twitter de rug toe te keren (vanwege de outages en beperkte communicatie) en enkel en alleen voor Friendfeed te kiezen of met Twit-Outs om aandacht vragen bij het Twitter [...] […] ben alvast niet één van die voorstanders (zoals Scoble) om Twitter de rug toe te keren (vanwege de outages en beperkte communicatie) en enkel en alleen voor Friendfeed te kiezen of met Twit-Outs om aandacht vragen bij het Twitter […]

]]> By: Matt http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-123 Matt Thu, 22 May 2008 04:47:06 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-123 "So if Twitter has known about these issues for more than a year, why hasn’t there been some sort of plan of action for when Ruby must go. A lot of the problems we’re seeing now might be due to the fact that Twitter has turned a blind eye to scaling up until now." Ruby and Rails aren't interchangeable terms - Ruby is the language, Rails is the framework. It's Rails' ORM - ActiveRecord- and the rest of its' magic that's now causing the bottlenecks - if we are to believe it's truly Rails causing the problems. Ruby is a programming language - and a wonderful one at that. Changing away from Ruby into another language won't stop downtime or 'fix' their problems. “So if Twitter has known about these issues for more than a year, why hasn’t there been some sort of plan of action for when Ruby must go. A lot of the problems we’re seeing now might be due to the fact that Twitter has turned a blind eye to scaling up until now.”

Ruby and Rails aren’t interchangeable terms - Ruby is the language, Rails is the framework. It’s Rails’ ORM - ActiveRecord- and the rest of its’ magic that’s now causing the bottlenecks - if we are to believe it’s truly Rails causing the problems.

Ruby is a programming language - and a wonderful one at that. Changing away from Ruby into another language won’t stop downtime or ‘fix’ their problems.

]]> By: Save Twitter with Open Source | Shannon Whitley http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-76 Save Twitter with Open Source | Shannon Whitley Sun, 18 May 2008 20:30:17 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-76 [...] has some major issues with customer satisfaction.  Regular, unexpected outages are causing significant frustration for its users and many are wondering what can be done to escalate the [...] […] has some major issues with customer satisfaction.  Regular, unexpected outages are causing significant frustration for its users and many are wondering what can be done to escalate the […]

]]> By: Shannon Whitley http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-75 Shannon Whitley Sat, 17 May 2008 23:07:50 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-75 I read this post and Chris' post. Great points that I hope @ev et al. will read and consider. Facebook went through this same period and I railed against them much in the same way. For some reason Web 2.0 companies don't seem to follow standard, time-worn development processes. You don't change things in the production environment: IT 101. I saw proof of this when the search bar bounced around the page one day on Twitter. And I have to wonder why Twitter is even bothering with mouseover effects when they can't keep the servers up. But enough bashing. Facebook finally got it right and implemented a better production migration process. Twitter can too, but when? I'd also argue that the Twitter service is pretty simple compared with Facebook or My Space. They've been experiencing problems for quite some time. If Rails is the issue, invest in rewriting some of the app. I'm a developer. I know how hard it can be to develop a scalable system, but I also know that being stubborn about bad choices doesn't fix the problem. Twitter is a great service and I'm tired of all the negativity, but the outages are frustrating. What can we do to help you, Twitter? I read this post and Chris’ post. Great points that I hope @ev et al. will read and consider.

Facebook went through this same period and I railed against them much in the same way. For some reason Web 2.0 companies don’t seem to follow standard, time-worn development processes. You don’t change things in the production environment: IT 101. I saw proof of this when the search bar bounced around the page one day on Twitter.

And I have to wonder why Twitter is even bothering with mouseover effects when they can’t keep the servers up.

But enough bashing. Facebook finally got it right and implemented a better production migration process. Twitter can too, but when?

I’d also argue that the Twitter service is pretty simple compared with Facebook or My Space. They’ve been experiencing problems for quite some time. If Rails is the issue, invest in rewriting some of the app. I’m a developer. I know how hard it can be to develop a scalable system, but I also know that being stubborn about bad choices doesn’t fix the problem.

Twitter is a great service and I’m tired of all the negativity, but the outages are frustrating. What can we do to help you, Twitter?

]]> By: Jacob Burke http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-73 Jacob Burke Sat, 17 May 2008 22:32:11 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-73 I think a great way that Twitter can alert users of upcoming outages is to send it out in the public timeline for all users to receive. If they can do it with ads in Japan, then they can leverage that to update the entire twittersphere. I think a great way that Twitter can alert users of upcoming outages is to send it out in the public timeline for all users to receive. If they can do it with ads in Japan, then they can leverage that to update the entire twittersphere.

]]> By: Andrew Feinberg http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-72 Andrew Feinberg Sat, 17 May 2008 22:26:05 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-72 Dude, you totally misrepresented Al3x's quote. He -never- said "rails doesn't scale," he said that to use it in a high usage application you need to either get rid of the slow dev-friendly stuff that makes it easy to code small stuff with, OR keep the friendly stuff and port the slow parts of the app. Dude, you totally misrepresented Al3x’s quote. He -never- said “rails doesn’t scale,” he said that to use it in a high usage application you need to either get rid of the slow dev-friendly stuff that makes it easy to code small stuff with, OR keep the friendly stuff and port the slow parts of the app.

]]> By: Ontario Emperor http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-70 Ontario Emperor Sat, 17 May 2008 21:30:28 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-70 To me, the most important is number 2. I could live with the other problems if they would tell us things as they're happening...not hours (or sometimes days) later. To me, the most important is number 2. I could live with the other problems if they would tell us things as they’re happening…not hours (or sometimes days) later.

]]> By: Isn’t Web 2.0 About US Taking Control? | introspective snapshots http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-69 Isn’t Web 2.0 About US Taking Control? | introspective snapshots Sat, 17 May 2008 16:49:47 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-69 [...] more than anything is for Twitter to realize that the technical problems may soon be dwarfed by the social problems. It’s in my own best interest that wherever I invest my conversation and build community [...] […] more than anything is for Twitter to realize that the technical problems may soon be dwarfed by the social problems. It’s in my own best interest that wherever I invest my conversation and build community […]

]]> By: Matt Brooks http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-66 Matt Brooks Sat, 17 May 2008 10:30:57 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-66 The "follow factor" is no longer accurate at tracking spammers. I have started to notice that spammers are following people and then immediatly unfollow people to keep their "follow factor" low. Once someone accepts their follow, the bot will follow back again resulting in two follow emails. The “follow factor” is no longer accurate at tracking spammers. I have started to notice that spammers are following people and then immediatly unfollow people to keep their “follow factor” low. Once someone accepts their follow, the bot will follow back again resulting in two follow emails.

]]> By: Scabr http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-65 Scabr Sat, 17 May 2008 05:48:19 +0000 http://jerseysuburbia.com/2008/05/16/five-things-twitter-shouldnt-be-doing/#comment-65 First thing Twitter Shouldn’t Be Doing: Be Unstable:) First thing Twitter Shouldn’t Be Doing: Be Unstable:)

]]>