Remix clone Hacker News

Can you explain why they have 3 concurrent cursor projects for the same code base?

alexjplant 2 days ago | parent | next [-]

Presumably to crank out multiple features at the same time. After spending some time writing project rules for Cursor I've gotten it to reliably implement end-to-end CRUD operations from a simple description of the fields and functionality. It's pretty neat and surprisingly accurate but it does take time to generate on the order of ~1k LOC so I understand the desire for parallelization. If you have a well-factored codebase with loose coupling, good abstractions, etc. this should be pretty doable without them stepping on each other.

▲

trashchomper 2 days ago | parent | prev [-]

I assume they're trying to work on three features at the same time

	▲	prescriptivist 2 days ago \| parent [-]
		Exactly, if you are doing copilot driven dev, then you are in a feedback loop with the agent and it's easier to have multiplexed ongoing "conversations" with the agent across discrete checkouts of the same codebase than it is to ask an agent to make a change, commit, checkout another branch, wait for the context to update/become aware, ask for a change, agree to it, commit, then switch back to another context. It's the kind of thing git worktrees was made for.