If people would be as patient and inventive to teach junior devs as they are with llms the whole industry would be better of.
[deleted]
Snorting the AGI with Claude Code
61–70 of 253 posts
Re: Snorting the AGI with Claude Code
#62On the one hand very cool. On the other hand, every time people are just spinning off sub-agents I am reminded of this: https://www.lesswrong.com/posts/kpPnReyBC54KESiSn/optimality... It's simultaneously the obvious next step and portends a potentially very dangerous future.
[deleted]
Re: Snorting the AGI with Claude Code
#63The terminal really is sort of the perfect interface for an LLM; I wonder whether this approach will become favored over the custom IDE integrations.
sort of, except I think the future of llms will be to to have the llm try 5 separate attempts to create a fix in parallel, since llm time is cheaper than human time... and once you introduce this aspect into the workflow, you'll want to spin up multiple containers, and the benefits of the terminal aren't as strong anymore.
Tmux?
Re: Snorting the AGI with Claude Code
#64[flagged]
[deleted]
Re: Snorting the AGI with Claude Code
#65Earlier quoted context omitted.
I'm sure people (esp engineers) know this. But imagine you're starting a company: would you try to deploy N agents (even if shitty), or take a financial/time/legal/social risk with a new hire. When you consider short-term costs, the math just never works out in favor of real humans.
What about the financial / legal / social risk of your AI agent doing something bad? You're only looking at cost savings, without seeing the potentially major downsides.
"What about the financial / legal / social risk of your AI agent doing something bad?"
the same way we treat it like human making mistake??? AI cant code themselves, someone command them to create something
Re: Snorting the AGI with Claude Code
#66If 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.
See if the promise was real: llms are great skill multipliers! Then it is the new renaissance of one developer businesses popping up left and right every day! Ain't nobody got time for corporate coercion hierarchy nonsense.
Hmm no news about that really
Re: Snorting the AGI with Claude Code
#67Earlier quoted context omitted.
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.
Maybe it's the senior devs who should be the ones to worry? Seniors' attitudes on HN are often quick to dismiss AI assisted coding as something that can't replace the hard-earned experience and skill they've built up during their careers. Well maybe, maybe not. Senior devs can get a bit myopic in their specializations. Whereas a junior Dev doesn't have so much baggage, maybe the fertile brains of youth are better in…
Wherever you look, the conclusion is the same - balance is required. Too many seniors, you get stuck in one way streets. Too many juniors, you trip over your own feet and diverge into unknown avenues.
Mix AI in, I don't see how that changes much at all... Juniors drive into unknown territory faster, Seniors get stuck in their niche just as well. Acceleration yes, fundamental change of how we work - I don't see it yet.
Re: Snorting the AGI with Claude Code
#68The terminal really is sort of the perfect interface for an LLM; I wonder whether this approach will become favored over the custom IDE integrations.
sort of, except I think the future of llms will be to to have the llm try 5 separate attempts to create a fix in parallel, since llm time is cheaper than human time... and once you introduce this aspect into the workflow, you'll want to spin up multiple containers, and the benefits of the terminal aren't as strong anymore.
dagger does this: https://www.youtube.com/watch?v=C2g3vdbffOI
Re: Snorting the AGI with Claude Code
#69The terminal really is sort of the perfect interface for an LLM; I wonder whether this approach will become favored over the custom IDE integrations.
as the models get better, IDEs will be seen as low level
Re: Snorting the AGI with Claude Code
#70The terminal really is sort of the perfect interface for an LLM; I wonder whether this approach will become favored over the custom IDE integrations.
sort of, except I think the future of llms will be to to have the llm try 5 separate attempts to create a fix in parallel, since llm time is cheaper than human time... and once you introduce this aspect into the workflow, you'll want to spin up multiple containers, and the benefits of the terminal aren't as strong anymore.
Who or what will review the 5 PRs (including their updates to automated tests)? If it's just yet another agent, do we need 5 of these reviews for each PR too?
In the end, you either concede control over 'details' and just trust the output or you spend the effort and validate results manually. Not saying either is bad.