Iterate rapidly to test environments, have more controlled releases to production. You can also use techniques like feature switches to roll out experimental f

Iterate rapidly to test environments, have more controlled releases to production. You can also use techniques like feature switches to roll out experimental features to only part of your userbase, although even then you'd ensure basic reliability first. To be honest, it sounds like you've confused 'iterate faster' with 'write crap code'. That's not what it means at all. It's HARDER to iterate faster with crap (presumably untested/untestable) code since you're piling technical debt upon technical debt. Clean, tested, maintainable code is essential for quick iterations to succeed.