When my wife and I watched the show I wrote a solver on the side so we always had the current probabilities and impossible combinations on the side.
I am thinking about making a website for it when the next season starts.
Also: in Germany at least they have 10 x 10 candidates from the start, but sometimes they add a 11th or even 12th of one gender so that there are double matches (e.g. 1 woman has two man as match and needs to find one of it to succeed). This raises the possible combination quite a bit.
Yes there's a gender fluid season and a season where someone had > 1 match, as well as people leaving part way through the season (apparently perfect matches are interchangeable...). All very interesting spins on the core problem to solve; would be really interested if anyone tries to tackle those seasons.
One point to keep an eye on is, if you are using (e.g.) AWS API Gateway with a custom authorizer, it caches the authentication response for a certain time.
This is not a problem of jwt, but makes the 'logout everywhere' and every black and whitelist need some more time.
I don't know if a designer would say, that it's well designed, but I am quite happy with https://kalle.co . No blog, just a small landing page with links to social profiles.
Small note: I wouldn't count the serverless framework as cloud agnostic. Yes you can use the framework for all major clouds but you have to adjust your project for that. Serverless does not abstract the events, function context or other service APIs which would be needed if it would be really cloud agnostic = you can deploy your project to different providers without changes.
I am thinking about making a website for it when the next season starts.
Also: in Germany at least they have 10 x 10 candidates from the start, but sometimes they add a 11th or even 12th of one gender so that there are double matches (e.g. 1 woman has two man as match and needs to find one of it to succeed). This raises the possible combination quite a bit.
reply