> the point of learning should not be to do something, but to expand your own mind and understanding of the world (and beyond)
I agree with your comment overall, but people have different reasons for learning and it may not be productive to tell them they are learning for the wrong reason. Let's celebrate all learning for I fear we are heading in a direction where it will become increasingly uncommon.
I agree with you. But do you remember when we could chat with a colleague about how much of a doofus our boss was without worrying that some automated system would possibly notify the boss about it? Nowadays big brother is always watching.
Maybe with very fast models you could request animation frames, e.g., frame 1) right foot at 12, left foot at 6; frame 2) right foot at 3, left foot at 9, etc.?
And instead of reporting tps, you would - of course! - report pfps (pelican frames per second).
I think it depends on what a memory system includes. Those that automatically inject relevant information into context are in my experience better than just md docs because agents often ignore, forget to read, or don't read md files in full.
It isn't ideal, but I am starting to write code (with AI tab completions) while waiting for LLMs. The tab completions are sometimes overeager and I wish I had more control over them, but at least I am not staring at "Thinking" all day. Having said that sometimes you have to monitor AI because, e.g., AGY CLI, often goes off the rails completely, including writing code outside of the "sandbox."
Thank you for explaining. Do you think there are still opportunities for stack optimizations to meaningfully speed up inference on single consumer-grade GPUs?
Or do you want it to speak to you too? I think this would have to be TTS on your phone. You can have ChatGPT speak to you but I don't see that feature in Codex.
Very nice! Would you have any recommendations for the leanest compatible "host"? Instead of adding this to my VSCode, I would rather use it as a separate app. Currently, I use a naked Zed install for Markdown because it launches faster than my system apps (and than Cursor, VSCode, etc.).
I like the idea. The demo music is very cool. The problem with using tone.js for such projects is, as I have learned the hard way, that it is hard to avoid issues like clipping; and AI agents are surprisingly bad at optimizing such apps.
I test nearly every new model that I can access on building a modular groovebox and they keep making the same mistakes. Even a 4-channel 16-step with a playhead can give them trouble.
I agree with your comment overall, but people have different reasons for learning and it may not be productive to tell them they are learning for the wrong reason. Let's celebrate all learning for I fear we are heading in a direction where it will become increasingly uncommon.