AI has made me wonder a lot lately about what it is that actually creates conscious experience, what is the actual physical mechanism that produces 'experience' (or is there a single valid mechanism, or rather just some property that can be expressed many ways). The more I think about it, the more I realize I have no fucking clue, and the more interested in the question I get.
This is speculation but maybe in the recurrent coupling between neuronal activity and the brain’s endogenous EM fields: neurons generate the field, the field ephaptically influences neurons, that closed loop may provide the physical integration associated with consciousness. A very active area of research so we will find out a lot more in the coming years.
I've landed here as well, but by force. I've actually tried to share some of the productivity and workflow tools I've built with AI that help automate portions of my work, specifically on target firmware debugging, and everyone at work just...ignored it. Didnt care. Of the small number of people who even stopped to look, a few of them were actively negative. Maybe I didnt sell it hard enough, but my job isnt to sell productivity tools internally (or even make them, i did it for myself). So, I'll keep making myself more productive and build tools for myself. And everyone else will just have to figure out their own path. I tried to help, but oh well.
Only if you double layers by layers instead of the whole stack (which IIRC is what nanbeige is doing).
To put it simply, if you have 3 layers A-B-C then A-A-B-B-C-C requires more compute but not more memory bandwidth, but A-B-C-A-B-C requires both twice the compute and twice the memory bandwidth for the same token generation speed.
Not quite. Looped models do the extra "thinking" inside the model's layers. So the token gets twice the number crunching performed on it before it gets spit out. I think of it as the first loop "kickstarts" the process, and the second loop refines it.
If he had one shortly after they launched, the suspension was truly terrible. R1T was clearly where all the work went and it's like no one even drove an R1S before they released it. Thankfully due to SW updates the suspension is absolutely night and day better, it went from making me violently sick to pretty nice. Assuming dudes car wasn't just a lemon, if he had and got rid of the R1S before the suspension got better I can 100% believe he hates the car.
I can understand when people say the code was the way part, but under the assumption that the system design and architecture are clean, code is high quality or the project is greenfield, and there is proper testing and validation. Then, sure, the lines of code aren't the hardest but that's only because that hardest work was front loaded and given a different name. Even then it's still not always easy.
Getting to a state where those assumptions are true is HARD. And takes a lot of careful programming.
Yes. Once it is true, the code is easy to write. But only because a lot of effort went into making it easy. And keeping it easy is also hard. Without focused effort to keep the code clean and easy to modify, it starts to rot.
reply