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.
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.
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.
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
Is that really true though? If you have a product people actually want, they’ll use it regardless of bugs
That’s sadly the opinion of a lot of tech companies.
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.
How much do you tolerate before switching sides? Think about Windows vs Linux. People don’t switch.