Live data from Hacker News

Agentic Coding Recommendations

lucumr.pocoo.org

11–20 of 210 posts

Re: Agentic Coding Recommendations

#11
Randomly, my advice: don't sleep on this.

Three or four weeks ago I was posting how LLMs were useful for one-off questions but I wouldn't trust them on my codebase. Then I spent my week's holiday messing around on them for some personal projects. I am now a fairly committed Roo user. There are lots of problems, but there is incredible value here.

Try it and see if you're still a hold-out.

Re: Agentic Coding Recommendations

#12
post #8

Earlier quoted context omitted.

Have you tried aider, and if so, how is it lacking compared to Claude Code in your opinion?

I only tried aider with hosted models and it's too expensive compared to Claude Code so I did not give it a real proper try.

How is it more expensive?

Re: Agentic Coding Recommendations

#14
post #8

Earlier quoted context omitted.

Have you tried aider, and if so, how is it lacking compared to Claude Code in your opinion?

I only tried aider with hosted models and it's too expensive compared to Claude Code so I did not give it a real proper try.

Aider is worth some tinkering for slightly different reasons than Claude Code.

I find agents do a lot of derpy shit for hard problems but when you've got fairly straightforward things to build it's nice to just spin them up, let them rip and walk away.

Aider feels more like pair programming with an agent, it can kind of be spun up and let rip, but mostly it tries to keep a tighter feedback loop with the user and stay more user directed, which is really powerful when working on challenging things. For stuff like codebase refactors, documentation passes, etc that tight loop feels like overkill though.

Re: Agentic Coding Recommendations

#15

Randomly, my advice: don't sleep on this. Three or four weeks ago I was posting how LLMs were useful for one-off questions but I wouldn't trust them on my codebase. Then I spent my week's holiday messing around on them for some personal projects. I am now a fairly committed Roo user. There are lots of problems, but there is incredible value here. Try it and see if you're still a hold-out.

[dead]

Re: Agentic Coding Recommendations

#16
So using agents forces (or at least nudges) you to use go and tailwind, because they are simple enough (and abundant in the training data) for the AI to use correctly.

Does this mean that eventually in a world where we all use this stuff, no new language/framework/library will ever be able to emerge?

Competing with the existing alternatives will be too hard. You won't even be able to ask real humans for help on platforms like StackOverflow because they will be dead soon.

Re: Agentic Coding Recommendations

#17
post #2

> This is not an advertisment for Claude Code. It's just the agent I use at the moment. What else is there? Alternatives that are similar in their user experiences are OpenCode, goose, Codex and many others. There is also Devin and Cursor's background agents but they work a bit different in that they run in the cloud. What do you recommand to get a Claude-code-like experience in the open-source + local llm ecosystem?

The Neovim plugin CodeCompanion is currently moving into a more agentic direction, it already supports an auto-submit loop with builtin tools and MCP integration.

Yes it's not a standalone CLI tool, but IMHO I'd rather have a full editor available at all times, especially one that's so hackable and lightweight.

Re: Agentic Coding Recommendations

#18

Earlier quoted context omitted.

I only tried aider with hosted models and it's too expensive compared to Claude Code so I did not give it a real proper try.

How is it more expensive?

You pay for aider with per-token pricing. Claude Code comes with a flatrate that gives you deep discounts.

Re: Agentic Coding Recommendations

#19
post #5
post #3

I find it excellent news that all the techniques that make agentic coding more efficient also make human coding more efficient. There was a worry that code would become big mud balls that only AI understand, but it looks like the opposite. Clear code is important for AI productivity, so it now matters even more, because the difference of productivity is immediately and objectively measurable. Before AIs what code was…

"There was a worry that code would become big mud balls that only AI understand, but it looks like the opposite." For now...

As long as interfaces are well defined, comprehensive tests are written, memory is safely handled and time complexity is analyzable, who cares what the rest of the code looks like.

I understand programming for the sake of programming, chasing purity and really digging into the creative aspects of coding. But I get that same kick out of writing perfect interfaces, knowing that the messier the code underneath is, the more my beautiful interface gets to shine. But transformers are offering us a way to build faster, to create more, and to take on bigger complexity while learning deeply about new domains as we go. I think the more we lean into that, we might enter a software golden age where the potential for creativity and impact can enter a whole new level.

Post reply on HN