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

Technology

37707 readers
7 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 10 points 1 year ago* (last edited 1 year ago) (1 children)

i remember a corporate rule came down that we needed something like 70% of all code unit tested for stability.

Damn were our getters and setters rock solid. No errors there. Business logic however...

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

Well, then the developers committed fraud, as getters and setters generally have very little logic. I'm surprised the code coverage reports failed to show the low coverage... You did have code coverage reports, rright?

[–] scrubbles@poptalk.scrubbles.tech 1 points 1 year ago (1 children)

Bruh it's a story, not a trial.

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

I find it a bit obnoxious to claim unit testing is a waste of time and then point to worthless testing of logicless code as proof.

All that illustrates is that worthless tests are worthless. Basically, a tautology. If one wants to convince people that tests are worthless, show how actual test coverage added no value.

The reason most coverage requirements are about 80%, is precisely that testing should not be done on code that has no business logic, like getters and setters.

So, testing the one thing for which tests are worthless is fraudulent behavior and ironically just makes their own jobs that much more painful.

[–] 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.