> Admittedly, the line between moving fast and breaking things and throwing money into a flame trench is rather thin, but it's only a problem if they ignore their data.
Not really. "Moving fast and breaking things" is relevant in software development circles, where a crash just means a restart and iterating means someone already on payroll has to spend some time fixing bugs.
This is not the case in real engineering fields. A crash has a far more profound implication on project viability, and a greater impact on cost and project deadline. Worst case scenario, it can cost people's lives.
These tradeoffs are far different in real engineering projects, to the point where in some domains an engineer can lose its ability to practice and even be thrown in jail.
Not really. "Moving fast and breaking things" is relevant in software development circles, where a crash just means a restart and iterating means someone already on payroll has to spend some time fixing bugs.
This is not the case in real engineering fields. A crash has a far more profound implication on project viability, and a greater impact on cost and project deadline. Worst case scenario, it can cost people's lives.
These tradeoffs are far different in real engineering projects, to the point where in some domains an engineer can lose its ability to practice and even be thrown in jail.