Sorry, but it's not. I've been prompting/fine-tuning LLMs since 2019, and have tried just about everything, ran tests, etc. etc. There's a reason most serious practitioners use XML prompts for almost everything.
@mattshumer_
-
Tool Call ID Mismatch Errors Fixed in AI Framework
By
–
It's SO good, and doesn't break with annoying tool call ID mismatch errors
-
Building Custom AI Tools Without Built-in Tool Calling
By
–
This is what I do! I just build it myself instead of relying on built-in tool calling 🙂
-
Optimized Prompts for Advanced AI Models
By
–
Oh, I meant that that looked like an optimized-for-o3 prompt!
-
Igor Taber leads insane second round with AI Matt
By
–
Thankfully @igorTaber was just as insane as me and led our second round after chatting with AI Matt!
-
AI Voice Clone for VCs: 2021 Innovation Ahead of Its Time
By
–
Haha we did this back in 2021, complete with an AI clone of my voice that VCs could chat with People thought I was insane back then
-
Structured Output Limitations in AI Systems
By
–
JSON output != JSON input I've had quite bad luck w/ forced structured outputs in general though
-
Claude Models Performance Evaluation by Serious Practitioners
By
–
almost every model, especially claude models try it. almost any serious practitioner will tell you the same.
-
Structured Tags in AI: From Simple to Complex Use Cases
By
–
Our use cases range from extremely simple (i.e. output three options in tags) to absurdly complex (super nested tags with counters, metadata, etc.) Prompt clearly, and it'll work.
-
Prompt engineering beats validation libraries for reliable outputs
By
–
We don't really. It just works. I've seen so many validation libraries and techniques come and go, but most serious builders I know don't bother with them. They're essentially just nerd traps. Prompt the model well, and it'll output the right format 99%+ of the time.