3 ms·
Exactly. The cardinal rule of competent software development is that you don't test quality into the software. The root causes were requirements churn, split d
by yggdrasil 13y ago
Exactly. The cardinal rule of competent software development is that you don't test quality into the software. The root causes were requirements churn, split development, and no project coordinator. Those would be nearly insurmountable on an average size project but were hopeless on this project. It's a marvel they were able to stabilize it to the point it's at.