I was fixing cache invalidation and this page was the right thing at the right time to help me understand the solution to the problem: https://grokipedia.com/page/Cache_busting_in_Vite#troubleshooting

AFAIK, that collection of information is a new synthesis of many different bits of documentation, and presented in a way that got me to understanding faster and more completely than reading the disparate threads.

As a mechanism for probing the model, is this not generalizable? Given my "truly novel integration of existing data" assumption, is there a way to successfully sample under-explored latent spaces of the model and get interpretable results once you bump the output into the "wikipedia writer" direction?

If you could "diff" a model to find where the weights changed the most during training/tuning, you could distill down what the model has learned in an interpretable format.

Comments URL: https://news.ycombinator.com/item?id=47645237

Points: 1

# Comments: 3

https://www.youtube.com/watch?v=TYIbgUy0T8U

He was first funded by FTX

I will never forget when I mixed up `if` and `of` during a routine backup.

`cat /dev/sda > /mnt/myDisk2` is so much safer, explicit, and in unix norms. It's also faster because you don't have to tune block size parameters.

Plus you can also do `pv /dev/sda > /mnt/myDisk2` to get transfer speed details.

Friends don't let friends use `dd` where `cat` can do the same job.

Art search for magic cards

Don't know if this is effective and I don't think management knows either, but it's what they're doing