My understanding is parallel branches allow multiple changelists to be applied to a single workspace. eg you can have multiple WIP fix branches active in your feature branch workspace and not worry about polluting your feature branch with unrelated/duplicated commits.
Worktrees are multiple workspaces, each in their own directory, sharing a single git repo. This is helpful because you reduce the overhead and the CLI command juggling for fully separate clones.
I have no idea what approach is better for your multi-agent scenario.
One of the authors, John Hughes did a talk on property-based testing at Clojure West some number of years back. Worth a watch if you're interested: https://www.youtube.com/watch?v=zi0rHwfiX1Q
Funny you should mention that. I just used a two sentence prompt to do something straightforward. It took careful human consideration and 3 rounds of "two sentence" prompts to arrive at the _correct_ transformation.
I think you're missing the cost of screwing up design-level decision-making. If you fundamentally need to rethink how you're doing data storage, have a production system with other dependent systems, have public-facing APIs, and so on and so forth, you are definitely not talking about "two sentence prompts". You are playing a dangerous game with risk if you are not paying some of it off, or at the very least, accounting for it as you go.
Yes, both. A good example why is for example, as muscle memory grows it will bias your note selection when improvising. Sometimes you really need to slow down to consciously force yourself to explore other sounds. Once you've done that, you need to wear it in again so it sounds natural in your playing.
Absolutely. You can get "locked in" to certain patterns / phrases just via muscle memory and familiarity. Need to balance that with a little improv to find new patterns phrases you like, and then can train those in via muscle memory.
That has been my comment to folks I know running these OpenClaw agents on Mac Minis. Some of them are very competent generally and are the type of people who I think historically would have told you why you shouldn't just `curl` and run some script to install something. For some reason when it comes to this stuff, when I bring up the possibility of their machine/connection/name/etc. being used for CSAM, they seem undisturbed. It is bizarre.
If it's to enable multi-agent scenarios, don't worktrees (at least in the local sense) allow for this?
reply