One of the hip terms that you hear a great deal in Silicon Valley is “fail fast.” This means to find out what does not work so you can move on to what does. It’s solid advice, for the most part.
However, failing in some enterprises’ IT shops may get you put out of the organization, so many IT pros avoid failure at any cost—or at least never declare failure, even if it means spending millions of dollars in dealing with ineffective systems that are costly to run or even hurt the business.
[ InfoWorld explains: What is cloud-native? The modern way to develop software. | Get started: Azure cloud migration guide. • Tutorial: Get started with Google Cloud. | Keep up with the latest developments in cloud computing with InfoWorld’s Cloud Computing newsletter. ]
For the cloud, you need to know when to declare a “fail,” when to hit the reset button and start from the beginning when doing migrations.
To read this article in full, please click here