From an inside look at Twitter’s problems with management, technology, and trolls:
At the same time, her defenders say, Harvey has been forced to clean up a mess that Twitter should have fixed years ago. Twitter’s backend was initially built on Ruby on Rails, a rudimentary web-application framework that made it nearly impossible to find a technical solution to the harassment problem. If Twitter’s co-founders had known what it would become, a third former executive told me, “you never would have built it on a Fisher-Price infrastructure.” Instead of building a product that could scale alongside the platform, former employees say, Twitter papered over its problems by hiring more moderators. “Because this is just an ass-backward tech company, let’s throw non-scalable, low-tech solutions on top of this low-tech, non-scalable problem.”
Calls to rethink that approach were ignored by senior executives, according to people familiar with the situation. “There was no real sense of urgency,” the former executive explained, pointing the finger at Harvey’s superiors, including current C.E.O. Jack Dorsey. “It’s a technology company with crappy technologists, a revolving door of product heads and C.E.O.s, and no real core of technological innovation. You had Del saying, ‘Trolls are going to be a problem. We will need a technological solution for this.’” But Twitter never developed a product sophisticated enough to automatically deal with with bots, spam, or abuse. “You had this unsophisticated human army with no real scalable platform to plug into. You fast forward, and it was like, ‘Hey, shouldn’t we just have basic rules in place where if the suggestion is to suspend an account of a verified person, there should be a process in place to have a flag for additional review, or something?’ You’d think it would take, like, one line of code to fix that problem. And the classic response is, ‘That’s on our product road map two quarters from now.’”
None of this means that Twitter is going to vanish soon — after all, COBOL is still around, and software legacies just hang around, decaying slowly, like an assortment of pseudogenes. But still, maybe you should consider jumping ship, since the one way to kill it is to erode its user base. Mastodon is out there, waiting for you with open arms.