I always thought T&& made sense as a movable reference. In order to move something, you need to change where the reference points, so conceptually you need a reference to the original reference to update it. (Effectively a double reference)

i < array.length or else you overflow.

I’ve realized that for a lot of things that a phone does, e-ink is too slow to refresh. Even web browsing becomes painful to navigate sometimes. Maybe a dual-screen approach would work with e-ink on one side and a regular screen on the other?

I will say, you can’t beat the satisfaction of tracking down the root cause and actually fixing the bug. I don’t understand why so many people meme about covering up bugs with crazy hacks. It’s not fun constantly looking over your shoulder to see if that bug has resurfaced. They start to pile up.

I think part of the problem is that LLMs stop learning at the end of the training phase, while a human never stops taking in new information.

Part of why I think AGI is so far away is because to run the training in real-time like a human, it would take more compute than currently exists. They should be focusing on doing more with less compute to find new more efficient algorithms and architectures, not throwing more and more GPUs at the problem. Right now 10x the GPUs gets you like 5-10% better accuracy on whatever benchmarks, which is not a sustainable direction to go.