The saying means that when creating something new for profit, don't worry too much about trying to figure out all the details beforehand and figure it out as you go. This will inevitably cause things to break, but being able to quickly fix that when it happens is the same skills needed to create new features as you go.

The saying does not work with large and complex established systems where breaking things wreak havoc.

[–] Soup@lemmy.world 20 points 3 weeks ago (3 children)

It also feels like they chase the “break things” part as if not breaking stuff is a bad thing, and like we should be proud of them for releasing broken and poorly tested updates.

Move fast, break things, fix the broken things, push update/product whatever. They keep forgetting the third step.

[–] JohnSmith@feddit.uk 7 points 3 weeks ago

I think there is another aspect that is important: limit the blast radius. Shit inevitably happens when you create something new and complex, and when it does, you’d rather minimise the impact where possible.

load more comments (2 replies)

load more comments (6 replies)