Getting Ready for Launch

The article references sites with healthcare information, military records, and more. The author states "Focus on availability, correctness, performance, and functionality, in that order... it might be tempting to fix the bug, but your only job in that moment is to put the site back in service".

It turns out some bugs can be security holes, or cost large amounts of money, or corrupt data, or trigger extreme exposures. So it's smart to understand a bug's risk, then choose what to prioritize-- because you may need correctness first, then functionality, then performance, and only then availability.

To get ready for launch, do your own work to prioritize your system quality attributes a.k.a. cross-functional aspects, non-functional requirements, quality of service specifications: https://github.com/joelparkerhenderson/system_quality_attrib...