Why our software never returns warnings
We at SSOReady spend a good chunk of our day talking about pretty minor product decisions. I mean stuff like should this button say ‘Done’ or ‘Close?’ For a company of our size (i.e., not very big), details like this might seem pretty tedious, maybe inconsequential – but we think it all adds up.
As we make decisions, we tend not to rely on firm rules. We basically improvise. We figure it’s best at our stage to make judgment calls. If we’re wrong, the thinking goes, we can reverse course pretty easily. After all, we’re still small enough that we get direct feedback from every single customer.
However, we have developed at least one firm rule: our software never returns warnings to developers. We enforce binary outcomes. Either the behavior’s exactly right or it’s a full-fledged error.
Our SAML single sign-on product allows only two states for SAML responses. A login may either have Succeeded or Failed (for an attempted login to remain In Progress indicates the absence of any response from an identity provider). By choice, we have no way to float warnings to our customers.
