2 ms·
Most often I think it's due to poor separation of concerns. The programmer is about to push an input down a stack of method calls several layers deep. There's t
by yock 14y ago
Most often I think it's due to poor separation of concerns. The programmer is about to push an input down a stack of method calls several layers deep. There's the success condition, the failure condition, then the exception which captures unexpected behavior from the rat's nest of code he just called.
- stcredzero 14y agoHow often can this be addressed with orthogonal finite state machines? (For example: one which embodies whatever business process, and another that embodies errors and failures with IO and the network.)