It's important to understand that sometimes all of the edge cases do matter. So it's not a bad reflex per se, it just isn't right for this circumstance. It's li

It's important to understand that sometimes all of the edge cases do matter. So it's not a bad reflex per se, it just isn't right for this circumstance. It's likely that they simply don't know how to make this judgement call. It might be helpful to come up with a list of all of those edge cases, then sit down with them and have an open discussion about what types of things matter. Help them to develop heuristics for assessing what does and doesn't matter at a particular phase, and then have a "known limitations" document. This document is also helpful bc when the client or management comes to you and says something doesn't work, you can point to this as a known and prioritized problem. In general, I'd say that desire to cover the edge cases is the better problem to have. I'd rather that than developers who aren't worried about gaps and issues.