Solid funding, thorough testing, failover, and developer skill should always be prioritized in mission critical software-driven systems. There is tons of room for failure in complex solutions. There is also a growing trend in software being manipulated beyond it's actual functional purpose into other categories like generating up-sales, in app purchases, and to embedding advertising into key features... Corruption of software functionality is a key threat to software stability in mission critical software, and in systems that people truly depend on and if it's not addressed and regulated properly, it will spiral out of control in the future.This applies not just to mission critical systems, it applies to cell phones that you pay for, televisions and cars people buy as consumers, because they are often mission critical to us.With every single project, control, security, cost cutting, and tight delivery deadlines pose a constant threat to reliability and utility of all software-driven solutions.Within IT companies, there are constantly well paid people working as decision makers that proclaim "I'm not really a technical person" on a regular basis.Frankly, if you're working in a position that has critical impact on technology-based decisions, YOU SHOULD ALREADY BE A TECHNICALLY AWARE PERSON, OR QUICKLY LEARN HOW TO BE A WELL INFORMED TECHNICAL PERSON, or step aside and let an accountable technical person serve in that role.Key decision making in software based development needs to more carefully involve people dedicated to understanding technical implications, constraints, and potential outcomes in addition now more than ever in addition to other skills like human psychology, marketing, risk management, and within the many other roles filled within mission critical IT organizations.Also, an emphasis on budget management by moves like undercutting developer salaries for key roles and/or pressuring less experienced developers to write mission critical production code is fine for entertainment-based social media apps perhaps, but not for pacemakers... Some systems, especially those with the highest level of critical importance need to be exempt from cost cutting and should never tolerate a temporary fix/workaround/and that "not a technical person" culture.