this post was submitted on 03 Dec 2023
59 points (100.0% liked)

Technology

37730 readers
751 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
you are viewing a single comment's thread
view the rest of the comments
[–] kent_eh@lemmy.ca 6 points 11 months ago (1 children)

Probably the "fail fast" design mentality

[–] cwagner@beehaw.org 14 points 11 months ago (1 children)

I know what you mean, but FWIW: You probably mean "move fast and break things". "Fail fast" is usually about not hiding/carrying with you potentially bad errors, and instead "fail fast" when you know there’s an issue. It’s an important tool for reliability.

An unrealistic example: Better to fail fast and not start the car at all when there’s abnormal voltage fluctuations, then explode while driving ;)

[–] Radiant_sir_radiant@beehaw.org 3 points 11 months ago* (last edited 11 months ago)

Maybe they actually meant "fail fast" because it's cheaper to build? It would certainly explain a lot.

Not quite sure myself if I'm kidding or not.