Decided not to wear the life jacket whilst kayaking in Thailand. A speedboat came around the corner, then straight at me, such that I rolled off the kayak into the water. Whilst I still was struck by the propeller, I expect that I'd be gone had I been wearing the jacket.
I was also extremely lucky that I ended up having down and got hit in the butt as, to others, there's nothing that suggests I was in such a traumatic accident.
All I want is named parameters so that I don't need to have N variations of the same method with different signatures, also particularly helpful for understanding boolean parameters.
Absolutely - and regarding Jordan, whilst Petra was a definitely worth the visit, there's so much more to Jordan that has me wanting to return, not least, the people.
Is that architecture helpful for a saas app that needs to support users from corporate customers using single sign-on via an OIDC or SAML provider like Azure AD or ADFS?
I looked into using Okta or Auth0 for this sort of setup, but both were prohibitively expensive for a saas app.
Can't help but think this was just a marketing error. Had they called the OS something like SurfaceOS instead of WinRT, perhaps the expectation would have been something more accepted, akin to iOS and MacOS.