It's why I said quickly and correctly. I think it's a cop out to say someone was slow because they were building it correctly. Famously, the old space shuttle software was developed very slowly because it had to be 100% correct at all times. Most software does not need that level of correctness. Part of a SE's job is to understand that.
Fast, quality, cheap.
Pick two.
I pay a lot of attention when someone claims to have solved a problem I suspect to be NP-hard. There are a lot of possible explanations, for example they may have an incorrect measurement function or they may have chosen a simpler related problem that isn't really NP-hard, or both.