The flipside of this philosophy is that you have to be able to revisit your decisions when your requirements change. This is a superpower that you want to have

The flipside of this philosophy is that you have to be able to revisit your decisions when your requirements change. This is a superpower that you want to have individually as an engineer but you need organisationally as a culture too. If you have that power then you when you need to write some similar code you can copy and paste, because you can trust that when you have a third use you will actually refactor properly. It means that you can get the service up and running quickly on a box you've got, because you can trust that if the service actually gets used your org will allow you the time to put it on the cloud properly. It's the most important part of agile - make the right decision for what you've got now, and then make a different one later.