YAML vs JSON for LLMs: Real Token Counts, Real Gotchas
YAML vs JSON for LLMs, measured with a real tokenizer: YAML cuts ~30% of tokens vs JSON, and one YAML parsing quirk already breaks GitHub Actions configs.
Tag archive
YAML vs JSON for LLMs, measured with a real tokenizer: YAML cuts ~30% of tokens vs JSON, and one YAML parsing quirk already breaks GitHub Actions configs.
Most of my "five-minute tasks" are not coding. They are chores: an API response that won't parse, a...
I inherited a Go service in March that returned JSON like this: { "user_id": 8821, ...
Reliable data serialization is one of those architectural concerns that often looks simple until an...
Publishing a multiple-choice question corpus as a CC BY 4.0 dataset: the fields worth storing twice, denormalised taxonomy, and the CSV BOM nobody warns you about.

JSON is used everywhere in web development, especially when working with APIs, configuration files,...
There is no developer.google.com endpoint for "give me the public reviews on this app." What the Play...
You've been there: an API returns a 400-line JSON blob, your editor won't highlight it, and the error...
I built a small Python tool for a practical invoice-automation problem: extracting embedded text from...
An export has a field in one record, null in another and no field at all in a third. Those are...
Sooner or later you have to put JSON inside a string: a payload stored in a database column, a field...

We gave two Claude models nine messy texts to turn into JSON. Both left unknown values empty and ignored a planted order; one wrapped every answer in…