logoalt Hacker News

kami23today at 1:47 PM1 replyview on HN

This is where most of my productivity gains have come, I have a special harness I move from project to project now that does my testing orchestration, lots of my work day is setting up a prompt or two early and just letting them loop till they return evidence that the feature is working having gone through the big QA loop.

I've slowly been optimizing for token use through the stack and Claude ends up making very tight for loops for most of the process and keeping token count even lower. It's been nice. A lot of my toil at work is just gone.


Replies

osigurdsontoday at 2:30 PM

I can see how you could avoid regressions this way, but what do you add to your harness to prove that a new feature is working?

show 2 replies