It’s fine to do that if you’re pre-customer and you’re just dabbling with a new idea. Once you are ready to go public though you need to be stable and secure. The big problem is when people try to apply the same development philosophy between established software and pre-alpha software.

[–] BleatingZombie@lemmy.world 13 points 9 hours ago

I agree. It heavily depends on the "things" you're breaking

If it's prod, that's bad

If it's your "fuck-around" branch, go for it

[–] OsrsNeedsF2P@lemmy.ml 8 points 11 hours ago (2 children)

Once you are ready to go public though you need to be stable and secure

Is that really true though? If you have a product people actually want, they'll use it regardless of bugs

[–] tatterdemalion@programming.dev 6 points 8 hours ago (1 children)

That won't be true once your competition catches up to you and your bug-riddled product is pissing off customers, pushing them towards your competitors.

[–] boonhet@sopuli.xyz 6 points 7 hours ago

I think move fast and break things is more what you do before you get any real competition, or to get better than the competition in some areas by taking shortcuts in others.

You stop doing this when you're the big dog. Then you embrace the image of reliability and stability.

[–] pennomi@lemmy.world 22 points 11 hours ago

That’s sadly the opinion of a lot of tech companies.