Hm… I don’t think you should let claude run for 5 hours with a ten line prompt.
You’ll get “something” but what you get is certainly not going to be what you wanted.
Look, its not complicated:
1) be precise in what you want
2) have a feedback loop to verify it.
3) check in often, not once a day.
> Migrate the payment endpoints from the old client to the new one. Done means: every endpoint uses the new client, the old client is deleted, and the test suite passes.
What end point? What test suite? What is a client?
Maaaaybe the model can infer it from your code, but look, if a human taking that jira ticket would go: what does this mean? …then your model (yes, even 5.5) is going to make a bunch of assumptions.
Correct assumptions? Maybe. Maybe not. …but do you really want to find that out hours later?
Just say:
> Plan out the following as a set high level tasks: …
Then, review the plan and tell it to execute the plan, maybe something like; after each step,
ensure the code base compiles and the tests pass.
Then, come back after one hour and make sure it’s on the right track.
Poorly specified long running tasks is a recipe for “rollback all those changes…”
You’ll get “something” but what you get is certainly not going to be what you wanted.
Look, its not complicated:
1) be precise in what you want
2) have a feedback loop to verify it.
3) check in often, not once a day.
> Migrate the payment endpoints from the old client to the new one. Done means: every endpoint uses the new client, the old client is deleted, and the test suite passes.
What end point? What test suite? What is a client?
Maaaaybe the model can infer it from your code, but look, if a human taking that jira ticket would go: what does this mean? …then your model (yes, even 5.5) is going to make a bunch of assumptions.
Correct assumptions? Maybe. Maybe not. …but do you really want to find that out hours later?
Just say:
> Plan out the following as a set high level tasks: …
Then, review the plan and tell it to execute the plan, maybe something like; after each step, ensure the code base compiles and the tests pass.
Then, come back after one hour and make sure it’s on the right track.
Poorly specified long running tasks is a recipe for “rollback all those changes…”