This made me think of the secretary problem.

Early in life it makes sense to move on more easily, not because we value people or partners less, but because we’re still figuring out ourselves and how the world works. There’s just more uncertainty.

Later, when we know more about who we are and what fits, it’s natural to switch less.

https://en.wikipedia.org/wiki/Secretary_problem

to the point, that it is reasonable to commit altogether to the choice.

In Poland you can get one without doctors referal (for CT you need one because of ionizing radiation exposure), it cost between 100-200$ in normal, reputable hospital (not one like from the street view).

Nice to be on a country where these facilities are not overwhelmed

Other way around, you are paying money to go to the head of the line, while the people with medical issues get it for free - but have to wait.

Which I wouldn’t assume based on an HN post.

You can buy a plane ticket.

Sadly that's a little too far for me to pop over for a day

vaguely related : synthetic homotopies visualisation tool - https://github.com/marcinjangrzybowski/cubeViz2

Did you played with cubical flavor of Agda? here is fun project of mine related to it : https://github.com/marcinjangrzybowski/cubeViz2 :)

secound, espeicaly together with elm street for generating code from Haskell

I like to skip the backend all together and write the Elm app directly to something like Hasura (GraphQL with authorization on top of PG).

From my experience ability to turn equivalences to equlities and vice versa is very usefull. Without this you are ending in setoid hell - intracable mess of isomorphism. I suspect that also Higher Inductive Types have lots of potential to simplify practical verification effords (apart from obvious usecases of quotients and truncations)

It is my understanding that HITs are just as easy to integrate into non-homotopy type theories as they are to HoTTs.

It is nice to see practical application of dependently typed language!

Looking through the GitHub repo it doesn't look to actually use any of the dependently typed features of Idris.

(And I see now at the end of the article that they mention this).

If this grows in the future, I'd be curious to see if the team starts to integrate any dependent types.

Contrary, formal methods could (in theory!!) give as way to assess correctness of software regardless of programmer qualifications.

previous video that led to wager : https://news.ycombinator.com/item?id=27330412

cubical Agda : https://github.com/agda/cubical is also worth mentioning int this context