Tell HN: I regret every single time I use AI

I try to not be fully against AI, so keep giving it a change, today again. I went for sport and gave opus 4.6 a medium sized task.<p>In every single step there were assumptions done that I don’t think are correct. I was a refactor and not all is Claudes fault. But since I did have bad experience I work through the changes line by line and honestly I think I would rather have done it from the start then to review the changes as Claude did a not working weird verbose refactor that didn’t help with anything.</p><p>When I refactor personally I don’t lose focus, I get the mental model, I apply the virtue of laziness and find 7 things that could be done better and ask myself 10 more things on the way (for which I actively use AI for exploration)</p><p>Also whenever I give AI a task I’m bored and I watch a Youtube video or read a HN article, when I do work on the code myself I’m not sure I’m so much slower if I know what I’m doing, given the cost of exploration, context switching, more iteration pipelines, ai time + my reviewing time.</p><p>Right now I feel the best way of utilizing AI is not having it sit in your code base but rather have it a browser or somewhere, that way you can use it as research tool, but you are in the code.</p><p>I also strongly recommend to test every single step that you are not 100% sure about AI, the more specialized your requirement is the more often it is wrong, especially with changing versions etc.</p><p>I did set up a shortcut to create a vitest test file from every function and strg + t to run it and alt + t to run the last test again, so even on changes in consumed functions I can easily run it.</p><p>The fast feedback loop is so enabling. Can really recommend.</p><p>How do you guys doing serious workflows (no fantasy apps) use AI atm?</p>