I don't know, just feels like a weird community response to something that is the equivalent to me of bash piping...
Snorting the AGI with Claude Code
121–130 of 253 posts
Re: Snorting the AGI with Claude Code
#122Earlier quoted context omitted.
>>Learning comes from grinding Says who? While “grinding” is one way to learn something, asking AI for a detailed explanation and actually consuming that knowledge with the intent to learn (rather than just copy and pasting) is another way. Yes, you should be on guard since a lot of what it says can be false, but it’s still a great tool to help you learn something. It doesn’t completely replace technical blogs, books…
Pretty much all education research ever points to the act of actually applying knowledge, especially against variable cases, to be required to learn something. There is no learning by consumption (unfortunately, given how we mostly attempt to "educate" our youth). I didn't say they don't or can't provide an educational benefit.
Re: Snorting the AGI with Claude Code
#123Earlier quoted context omitted.
Pretty much all education research ever points to the act of actually applying knowledge, especially against variable cases, to be required to learn something. There is no learning by consumption (unfortunately, given how we mostly attempt to "educate" our youth). I didn't say they don't or can't provide an educational benefit.
Some of the best software learning I ever had when I was starting out was following along with video courses and writing the code line by line along with the instructor... or does this not count as "consumption"?
That's application. Then presumably you started deviating a little bit from exactly what the instructor was doing. Then you deviated more and more.
If you had the instructor just writing the code for every new deviation you wanted to build and you just had to mash the "Accept Edit" button, you would not have learned very effectively.
Re: Snorting the AGI with Claude Code
#124Earlier quoted context omitted.
One thing that I am not liking about the LLM world is that it seems to be tilting several things back in favor of BigCorps. The open source world is one where antirez, working on his own off in Sicily, could create a project like Redis and then watch it snowball as people all over got involved. Needing a subscription to something only a large company can provide makes me unhappy. We'll see if "can be run locally" mod…
This is some nightmare fuel vendor lock-in where the codebase isn't understood by anyone and companies have to fork over more and more otherwise their business couldn't grow, adapt, etc
I, for one, welcome our new LLM overlords.
Re: Snorting the AGI with Claude Code
#125If people would be as patient and inventive to teach junior devs as they are with llms the whole industry would be better of.
You pay junior devs way way way more money for the privilege of them being bad. And since they're human, the juniors themselves do not have the patience of an LLM. I really would not want to be a junior dev right now... Very unfair and undesirable situation they've landed in.
I hope you don't think that what you're paying for an LLM today is what it actually costs to run the LLM. You're paying a small fraction.
So much investment money is being pumped into AI that it's going to make the 2000 dot-com bubble burst look tiny in comparison, if LLMs don't start actually returning on the massive investments. People are waking up to the realities of what an LLM can and can't do, and it's turning out to not be the genie in the bottle that a lot of hype was suggesting. Same as crypto.
The tech world needs a hype machine and "AI" is the current darling. Movie streaming was once in the spotlight too. "AI" will get old pretty soon if it can't stop "hallucinating". Trust me I would know if a junior dev is hallucinating and if they actually are then I can choose another one that won't and will actually become a great software developer. I have no such hope for LLMs based on my experiences with them so far.
Re: Snorting the AGI with Claude Code
#126Asking it to explain rust borrow checker is one of the worst examples to demonstrate its ability to read code. There are piles of that in its training data.
A complete waste of time for important but relatively simple tasks.
Re: Snorting the AGI with Claude Code
#127Not trying to be rude here, but that `last_week.md` is horrible to me. I can't imagine having to read that let alone listen to the computer say it to me. It's so much blah blah and fluff that reads like a bad PR piece. I'd much rather scan through commits of the last week. I've found this generally with AI summaries...usually their writing style is terrible, and I feel like I cannot really trust them to get the facts…
Im so over this timeline.
Re: Snorting the AGI with Claude Code
#128Re: Snorting the AGI with Claude Code
#129Not trying to be rude here, but that `last_week.md` is horrible to me. I can't imagine having to read that let alone listen to the computer say it to me. It's so much blah blah and fluff that reads like a bad PR piece. I'd much rather scan through commits of the last week. I've found this generally with AI summaries...usually their writing style is terrible, and I feel like I cannot really trust them to get the facts…
Yeah I was done at "What happened here was more than just code..." -_-
Re: Snorting the AGI with Claude Code
#130I’m biased [0], but I think we should be scripting around LLM-agnostic open source agents. This technology is changing software development at its foundations—-we need to ensure we continue to control how we work. [0] https://github.com/all-hands-ai/openhands
This looks like a good resource. There are some pretty powerful models that will run on a Nvidia 4090 w/ 24gb of RAM. Devstral and Queen 3. Ollama makes it simple to run them on your own hardware, but the cost of the GPU is a significant investment. But if you are paying $250 a month for a proprietary tool it would pay for itself pretty quickly.