Skip Navigation

Twitter, Threads, and the misunderstood nature of engineering

Complex internet services fail in interesting ways as they grow in size and complexity. Twitter's recent issues show how failures emerge slowly over time as relationships between components degrade. Meta's quick launch of Threads demonstrates how platform investments can compound over time, allowing them to quickly build on existing infrastructure and expertise. While layoffs may be needed, companies must be strategic to maintain what matters most - the ability to navigate complex systems and deliver value. Twitter's inability to ship new features shows they have lost this expertise, while Threads may out-execute them due to Meta's platform advantages. The case of Twitter and Threads provides a lesson for companies on who they want to be during times of optimization.

49

You're viewing a single thread.

49 comments
  • This is a shitty take. Twitter ran perfectly fine before Musk took it over.

    Turns out if you don't pay your hosting bills, or your office building bills, fire most of your engineers (after annoying them with bullshit) and making rash decisions without consulting people with technical know-how your service goes to shit.

    Musk was stupid enough to DDOS his own service because he doesn't understand it. Blocking public access to tweets while having tweets embedded in millions of websites turned out to be a really bad idea. Simply because Twitter engineers always expected Tweets to be publicly available, so they kept retrying to fetch the data. There's probably a hundred+ developers at Twitter who could have told Musk that little tidbit.

    This is 100% on the egomaniacal billionaire and has nothing to do with the technology.

You've viewed 49 comments.