- I think about what work needs to be done, how it ties into the existing architecture, and how completion is going to make me money / solve a problem
- Start CC (usually in yolo / '--dangerously-skip-permissions' mode), tell it to read relevant files or investigate how x works now, don't code anything.
- Explain the problem to it, still don't code anything but ask it how it's going to solve this. If I'm satisfied that it's looking in the right direction, let it rip
- Wait for results, intensely manually QA whatever comes out. Take a cursory glance at the diffs in my IDE, to see if I generally approve of and understand what its doing
I can't QA faster than a single claude code agent produces output. While I test the output of step n, I sometimes let it continue on step n+1, but more than that is beyond me ATM.
Very curious to learn how others are going beyond this! Right now I don't see an immediate path beyong this for myself, so if you have some tips or another way of doing thing entirely, I'd be very grateful!
Working for a few different clients atm as a freelancer:
Postgres etl pipelines; python glue code around a computer vision model; some rest api integrations to a frontend (outside of my direct control); an llm-backed sql generator that integrates with legacy shitware; a swift ios/macos app...
I agree that I need to invest heavily in testing infrastructure, thanks. My work is pretty heterogeneous, so I kinda put that on the backburner as there's always more pressing short term stuff to tackle...
- I think about what work needs to be done, how it ties into the existing architecture, and how completion is going to make me money / solve a problem
- Start CC (usually in yolo / '--dangerously-skip-permissions' mode), tell it to read relevant files or investigate how x works now, don't code anything.
- Explain the problem to it, still don't code anything but ask it how it's going to solve this. If I'm satisfied that it's looking in the right direction, let it rip
- Wait for results, intensely manually QA whatever comes out. Take a cursory glance at the diffs in my IDE, to see if I generally approve of and understand what its doing
I can't QA faster than a single claude code agent produces output. While I test the output of step n, I sometimes let it continue on step n+1, but more than that is beyond me ATM.
Very curious to learn how others are going beyond this! Right now I don't see an immediate path beyong this for myself, so if you have some tips or another way of doing thing entirely, I'd be very grateful!
imho I think you benefit from better testing infra, as manual qa is your bottleneck. if you don't mind, what software is this?
Working for a few different clients atm as a freelancer:
Postgres etl pipelines; python glue code around a computer vision model; some rest api integrations to a frontend (outside of my direct control); an llm-backed sql generator that integrates with legacy shitware; a swift ios/macos app...
I agree that I need to invest heavily in testing infrastructure, thanks. My work is pretty heterogeneous, so I kinda put that on the backburner as there's always more pressing short term stuff to tackle...
1 reply →