When software quality is not the most important thing?

There are quite a few times when one does not need to adhere to a high software quality standard. For example, if you are realizing a concept and you want to iterate through the design to understand the product better. So you want to optimize the development for fast release. Nothing is more important than speed of pushing the product in production. In this scenario, you build the software as quick as possible avoiding any complex issues that can consume your time. This is exactly what is in practice in the internet industry for feature based or functional development. Of-course this is not always true. For example if Netflix offers you a slow web site with a crappy search engine with it, you will not enjoy the web site. However, still, one can focus on developing high quality softwares where it directly add value to the business. For all search engine companies, performance is a big deal and the code needs to be written carefully to allow fast innovation in the application layer. Code quality is important for that. Increasingly, there is a trend for using better and safer programming languages in the industry that takes care of a lot of concerns related to code quality. For example, if you have an application written in OCaml or Scala, they are definitely better suited for debugging. The point of this writing is that I realized increasingly in the internet industry one can safely ignore the aspects of code quality until and unless spending time in that gives some amount of value. Stroustrup is right in his article that we are in the industry is in perpetual rush and he commented that it is hard to work on code quality in such a rush. I somehow believe the language in future will take care of the quality issues to some extent and currently Industry rarely requires the kind of quality that Stroustrup had in his mind when he gave the interview to Business Insider.