> Which resulted in a spaghetti mess of over engineered code that still had bugs, and still didn't meet requirements, even after 100's of hour of reviews. One

> Which resulted in a spaghetti mess of over engineered code that still had bugs, and still didn't meet requirements, even after 100's of hour of reviews. One would think the first check in any review is "does this code do what it should do?" and stop the review right there if it doesn't. As a professor of mine once said "code that crashes fast and efficient doesn't help anyone."