upvote

points

by fhd26 hours ago |
comments
upvoteby suzzer993 hours ago|
next
[-]
Does good design up front matter as much if an AI can refactor in a few hours something that would take a good developer a month? Refactoring is one of those tasks that's tedious, and too non-trivial for automation, but seems perfect for an AI. Especially if you already have all the tests.
reply
upvoteby qudat46 minutes ago|
parent|
next
[-]
I’m constantly using code agents to work on feature development and they are constantly getting things wrong. They can refactor high level concepts but I have to nudge them to think about the proper abstractions. I don’t see how a multiagent flow could handle those interactions. The bus factor is 1, me.
reply
upvoteby Jensson44 minutes ago|
parent|
prev|
next
[-]
> Especially if you already have all the tests.

Most tests people write have to be changed if you refactor.

reply
upvoteby veilrap2 hours ago|
parent|
prev|
[-]
Upgrades, API compatibility, and cross version communication are really important in some domains. A bad design can cause huge pain downstream when you need to make a change.
reply
upvoteby echelon4 hours ago|
prev|
next
[-]
I'm using Claude Code (loving it) and haven't dipped into the agentic parallel worker stuff yet.

Where does one get started?

How do you manage multiple agents working in parallel on a single project? Surely not the same working directory tree, right? Copies? Different branches / PRs?

You can't use your Claude Code login and have to pay API prices, right? How expensive does it get?

reply
upvoteby ecliptik4 hours ago|
parent|
next
[-]
Check out Claude Code Team Orchestration [1].

Set an env var and ask to create a team. If you're running in tmux it will take over the session and spawn multiple agents all coordinated through a "manager" agent. Recommend running it sandboxed with skip-dangerous-permissions otherwise it's endless approvals

Churns through tokens extremely quickly, so be mindful of your plan/budget.

1. https://code.claude.com/docs/en/agent-teams

reply
upvoteby bernardom3 hours ago|
parent|
prev|
[-]
git checkout four copies of your repo (repo, repo_2, repo_3, repo_4) within each one open claude code Works pretty well! With the $100 subscription I usually don't get limited in a day. A lot of thinking needs to go into giving it the right context (markdown specs in repo works for us)

Obv, work on things that don't affect each other, otherwise you'll be asking them to look across PRs and that's messy.

reply
upvoteby cronin10158 minutes ago|
parent|
[-]
Look into git worktrees and thank me later!
reply
upvoteby briantakita4 hours ago|
prev|
[-]
I am now releasing software for projects that have spent years on the back-burner. From my perspective, agent loops have been a success. It makes the impractical pipe-dream doable.
reply
upvoteby Nadya4 hours ago|
parent|
next
[-]
Yeah, I have a never ending need of things I could easily make myself I I could set aside 7-10 hours to plan it out, develop and troubleshoot but are also low priority enough that they sit on the back burner perpetually.

Now these things are being made. I can justify spending 5-10 minutes on something without being upset if AI can't solve the problem yet.

And if not, I'll try again in 6 months. These aren't time sensitive problems to begin with or they wouldn't be rotting on the back burner in the first place.

reply
upvoteby sarchertech3 hours ago|
parent|
prev|
[-]
That’s completely ignoring the point of the person you are responding to. They weren’t talking about small greenfield projects.
reply
upvoteby briantakita1 hours ago|
parent|
[-]
Agent loops also enables the "hard discipline" of making sure all of the tests are written, documentation is up to date, specs are explicitly documented, etc. Stuff that often gets dropped/deprioritized due to time pressure & exhaustion. Gains from automation applies to greenfield & complex legacy projects.
reply