3 ms·
> some functionality wasn't specified and there's an edge case Edge cases are extremely rare. If they weren't they'd not be an edge case. But, we should still
by chooseaname 6y ago
> some functionality wasn't specified and there's an edge case
Edge cases are extremely rare. If they weren't they'd not be an edge case. But, we should still try and build robust systems and not allow the system to be in an unknown state. It isn't, "I have to think of all the possible cases." No, it's "These are the possible cases, nothing else is allowed."
If the cases were not specified, as you mention, then that is not completely a dev issue.
- gowld 6y agoEdge cases are common. Corner cases are rare.
- eindiran 6y agoI'm not familiar with this distinction: what is the difference you're pointing to here?
- gowld 6y agoTake a look at polytope. Edges are easier to hit than corners. If you start in a random place and move in any direction, you will eventually hit an edge. But you might never hit a corner.
- eindiran 6y agoIn case anyone was wondering the actual definitions: An edge case is a problem or situation that occurs only at an extreme (maximum or minimum) operating parameter. For example, a stereo speaker might noticeably distort audio when played at maximum volume, even in the absence of any other extreme setting or condition. [0] A corner case (or pathological case) involves a problem or situation that occurs only outside of normal operating parameters—specifically one that manifests itself when multiple environmental variables or conditions are simultaneously at extreme levels, even though each parameter is within the specified range for that parameter. [1] [0] https://en.wikipedia.org/wiki/Edge_case https://en.wikipedia.org/wiki/Edge_case [1] https://en.wikipedia.org/wiki/Corner_case https://en.wikipedia.org/wiki/Corner_case