As the Mythbusters frequently said, “Failure is always an option.”
Nobody gets everything right the first time, all the time. Developers and DBAs need to be able to experiment and try new things to learn what works best in their environment. Granted, it is generally easier for developers to do that since code that fails QA just goes back to development for another pass. A DBA’s changes can break things for the entire development team if things go sideways. Then there are a group of developers looking for something to do while the database changes are rolled back via scripts or a restore. Still worth the lessons learned.