Which is what I meant by, "you need to be very deliberate with it", you have to spend a lot of time on the inputs to get good outputs. Which makes it feel a fair bit less like "Intelligence" and a lot more like a calculator.
Context is everything. Whether they were talking to your junior employee, or to an LLM, if you don’t say what it is, you want don’t be surprised when it’s left to interpretation and comes out wrong.
Specifically, Claude coat is really good at making markdown files of plans and if you review them add in context, you can let it run a little more free than you would otherwise.
If you don’t feel like giving it, the right amount of context, make the job smaller, where there’s just less of it to begin with.
I wouldn’t tell my interns to change the formatting of these printf statements, because I don’t feel like it, but Claude does that stuff pretty great and doesn’t complain as much.
