In May-June last year, there was noise in the Twitter and developer communities about delays and unreliable service from the popular microblogging platform. Jeff Atwood from Coding Horror suggested Twitter was a victim of its own success. Twitter fought back, working hard to deal with the service issues that its meteoric rise had brought. A year on, and the same or similar issues are bubbling up. Who or what was to blame: the management? the developers? Ruby on Rails?