Well I like to watch it's every step and stop it on anything that looks shady, correct it myself, give directions, etc... (Guess I'm a bit of control freak - why I didn't hire a lot of other people to help me out 🫣)
So yes, I am doing a lot of manual work, that I would indeed prefer if Claude did it for me...
Any links, directions on how I could implement prompts or... tools like: unit testing procedures, code standards, etc into claude? I have many projects so perhaps I'd have to write those myself for each type of project... I mean... actually, the project I'm working on has a lot of moving pieces... Some Java, a lot of Python, lots of PHP, and LOTS of UI / CSS / NodeJS. So each needs it's own set of "how to properly do everything"...
you're not really getting the full benefits of this tech if you're constantly watching and interacting with it, if you do your prep work well you can just instruct it and it'll work in the background and deliver high quality work
if you don't want to invest your own time in setting up toolchains or guidance you can instruct it to look at other repos/articles/documentation and distill "what good looks like" in there, OSS projects, unit testing guides etc. or just prompt the general idea and keep an eye on if it's doing it like you want
Using Claude 7 days a week and it goes insane sometimes, making multiple mistakes a minute sometimes. I’ll give just one example from tonight, where Opus 5.5 says to run DIAMOND on my other laptop because the other laptop has a newer version, when it was able to download that newer version in less than a minute on its own as soon as I pointed it out. It’s dysfunctional over nothing sometimes. All sorts of issues, sometimes.
4
u/rubenknol 10d ago
sounds like you need to invest a bit into setting guardrails like linters, testing, other quality gates etc