4,836 karma · joined March 13, 2008
You could certainly try cloning the examples and messing with them: turning some number between 0 and 1 in the code into (mouseX/screenwidth) could prove interesting!
Most of these sites have a culture of learning from modifying and remixing other examples; just give credit where due
"Gentle study" is a bit unusual.
"Gentle ping" or "Gentle nudge", and especially "Gentle reminder", are starting to get a bit more annoying, but I think the intention there is try to convey the opposite of being demanding, but over a textual medium. ¯\_(ツ)_/¯
It was terrifying. I had just seen my mom taken by Alzheimer’s (or something similar) way too young, and thought my life was over.
All the tests coming back negative, making a point of hanging out with friends, returning to the office, and getting enough sleep seemed to help, and it slowly started getting better.
Basically every other IDE probably does it too by now.
I mostly blundered my way through this through this recent round of tons of interviews, and by the end of it, my "Tell me about a time when…" doc is actually what it should/could have been at the start!
I suspect at a "sensible" breakdown (trying to avoid the "How long is my coastline?" problem), which is presumably something akin to Zipfian, the main uses will actually account for most energy usage.
If anyone can find a breakdown at the level of granularity that "all deep learning" would make sense, let me know: so far my Googling has led primarily to either detailed breakdowns of energy _sources_, or high-level breakdowns of use at the level of "industry", "agriculture", or "residential use".
Not that I think giving away most of his money isn't admirable. But I think he'll still qualify for "he died rich".
The Commodore 64 is _so_ much better for graphics and sound it's not even funny, but if you look at the timelines, it came along a _while_ later than the Apple II.
I should probably just go read Goose's code…
I have to say, the endorsements at the end somehow made this seem worse…
tl;dr many of the LLMs use byte-pair encoding to create tokens. You take a set of documents, and then form tokens by repeatedly merging the most common pair of tokens. The initial set of tokens is 256 raw bytes. And the text is typically represented in utf-8.
I expect that although the LLMs can understand arbitrarily but cleanly offset unicode code points by (eventually) noticing the final byte of each sequence, they would do markedly worse on actually processing and completing on them, because they will not have been reduced to the normal set of tokens. However, if the text is actually output cleanly converted, either in internal thinking tokens or in the beginning of the response, they should do fine.
Understanding tokenization is surprisingly useful, even if that video seems awfully long to devote to such a tedious subject. Even Karpathy doesn't like it!