I am guessing that the first engineer was right. Usually there is not one solution to the problem and judging who's the slacker by estimates might be wrong. You can usually hack something up quick, but making a strong and lasting solution requires more time.

Judging who the slacker is by estimates is wrong, period.

There's a habit of technical folks to come to conclusions they shouldn't, and this is a perfect example. It generally manifests itself in interviews where the technical interviewer will come to conclusions that don't necessarily follow, only in this case it's not in an interview, but with respect to fellow co-workers.

I mean, you can see the hubris in the poster, who would have you believe that they're somehow "training" their management to "spot poor co-workers". Yeah, ok.... sure you are. Because managers are like monkeys apparently?

Cause the all night hero did not actually solved the issue, just made it less visible for release checklist purpose. Which is not the same as fixing it for users who kept complaining.