https://youtu.be/P5eO7BNyJao?si=45zxrLUsY9AMUg6B
I feel like there was not enough fuss about what he showed off this year considering how many programmers (historically myself included) cared about checking/enforcing structure on a potentially nested thing, spec in usage has proved to be good for external boundaries but not great for internals
I remember we used to code something like:
class User { name age username password }
etc all the time but would end up having to make everything optional so that we could use the type hint against the age method and the auth method when we had partial information for the object
Obviously not an optimal design and can be broken down into yet more types and then composed together but I'm not a huge fan of object of object of object type situations — anyway my point is that Rich showed that we can just do the checks in context using deconstructing and in a reusable way rather than trying to declare a type once centrally and then cram that into everything else
I haven't explained it very well — I wanted to do a blog on it but just watch the video its one of the few things I got excited about even though I don't really code directly any more - the sad thing is current LLMs won't even use the technique because its not in their training sets and that still matters I've noticed for what they do