roncesvalles
Joined 4 years ago
Joined 4 years ago
I rushed to the Claude platform console and was expecting to see a 4 figure usage bill or something. Luckily there was no usage.
But imagine if I were traveling. Even a rot13 of the key would've bought me enough time to rotate.
2 lessons:
- don't name your env var "CLAUDE_API_KEY". Call it "ARG_1" or something
- at least do some obscurin' so that the value doesn't start with "sk-ant..."
LLMs for many months have been at a level where if you know exactly what you want, you can simply let the LLM bang out an implementation and never have to read it. But outside of simple problems, you probably don't know what you exactly want.
That being said, I've had considerable success ending every prompt with "ask me for any further details that I haven't considered" or some variation thereof.
This has very interesting implications for everything in the world, btw. Correctness does not track majority consensus.
This Microsoft deal for the large part is not being offered to software engineering orgs.
For work in which you are in the loop, absolutely. Do people not value their own time or something? Why in the world would you use less than the best LLM available to you? You're not going to run out of the $20 plan even if you use Opus 5.5 at xhigh and code 8 hours/day (assuming you're doing it piecewise using a Claude product) so what exactly are you conserving by using something inferior?
For large continuous volumes of programmatically submitted LLM tasks, sure.
Like that old adage "that's a feature not a product" - Jev is just a system prompt, not a product.