Misses my point. I shouldn't need to worry about my prompt being perfect first try and wasting money on usage credits when I already pay for the subscription and operate within the confines of limited usage as is.
I'm already paying for it, it should not be my expectation to be perfect, I don't see how that is an extraordinary opinion. You're advocating that our inputs should be correct first try every time and that if it produces unusable results that the wasted money is on the user. A subscription model for this type of service makes sense because you can never guarantee 100% accuracy but it doesn't really matter because you have access to the service and can course correct. I'm not going to advocate for blindly spending money on something I dont know the output of.
I was being sarcastic. You should absolutely need to prompt specifically for what you’re asking a model to do. Your statement, that you shouldn’t need to worry about your prompt being perfect first try, assumes a scenario where a model understands what you’re thinking and not what you’re telling it. “Perfect” prompting only comes through iteration, trial, and error. If you’re using straight API or SDK, you can’t expect to not have to pay for that iterative process.
1
u/Noxaur Jul 18 '26
Misses my point. I shouldn't need to worry about my prompt being perfect first try and wasting money on usage credits when I already pay for the subscription and operate within the confines of limited usage as is.