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.
It's hard to imagine any system where half (or more) of your total earnings being taken is justified. I have no problem paying taxes, and mine could be noticeably higher without any negative day-to-day impact, for sure. I think there's a lot of FUD and fear-mongering around marginal tax rates but if your total tax bill is 50%+ something is very wrong.
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.
If Java had anonymous (structural) records, then named arguments could just be a function with a parameter that has a record structural type.
It could even be given syntactic sugar, something like:
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.
We integrated one third party provider into our AWS Cognito as a test - Google. The idea was to allow many and myriad third party providers to integrate with it, and we wouldn't have to bother to do any of the integration: just configure the Cognito and the other sides, and our app logic does not have to care (but can get that info from the JWT payload if it cares).
Yes, exactly: you use a fast data store such as redis or memcached.
As a user performs activities, this may involve a scenario requiring escalation or revocation of authorization roles and corresponding permissions. Invalidate cache at this moment. Lazy cache updated authorization info upon next request.
