this post was submitted on 12 Jul 2023
147 points (100.0% liked)

Technology

37717 readers
466 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] scrubbles@poptalk.scrubbles.tech 1 points 1 year ago (1 children)

Yes. That was the joke of it all. That a useless business rule that came down made developers more focused on hitting a metric rather than building useful tests. Thank you for explaining my own story to me.

[–] MasterBuilder@lemmy.one 1 points 1 year ago

Aha, well I like to think I would have picked up on the joke if this was an in-person discussion. I've heard that talking point as a serious condemnation of automated unit tests.