๐Ÿฏ๐Ÿด% ๐—ฏ๐—ฒ๐˜๐˜๐—ฒ๐—ฟ ๐—”๐—œ ๐—ฎ๐—ฐ๐—ฐ๐˜‚๐—ฟ๐—ฎ๐—ฐ๐˜†. ๐—ก๐—ผ ๐—ป๏ฟฝ...
# good-reads
v
๐Ÿฏ๐Ÿด% ๐—ฏ๐—ฒ๐˜๐˜๐—ฒ๐—ฟ ๐—”๐—œ ๐—ฎ๐—ฐ๐—ฐ๐˜‚๐—ฟ๐—ฎ๐—ฐ๐˜†. ๐—ก๐—ผ ๐—ป๐—ฒ๐˜„ ๐—บ๐—ผ๐—ฑ๐—ฒ๐—น. ๐—ก๐—ผ ๐—ป๐—ฒ๐˜„ ๐—ฑ๐—ฎ๐˜๐—ฎ. ๐—๐˜‚๐˜€๐˜ ๐—ฏ๐—ฒ๐˜๐˜๐—ฒ๐—ฟ ๐—ฐ๐—ผ๐—ป๐˜๐—ฒ๐˜…๐˜. Thatโ€™s the headline from a controlled NL-to-SQL experiment discussed by Manoj Shanmugasundaram in Metadata Weekly. Across 522 query evaluations, the only variable that changed was context quality โ€” and it made all the difference. Concise, high-signal context (business definitions, SQL patterns, domain rules) drove a 38% accuracy gain. Verbose, catalog-style documentation? Performance dropped and costs rose. More words diluted the signal. The biggest lift wasn't on simple or extreme queries. It was on medium-complexity ones โ€” the joins and aggregations that make up everyday analytics work โ€” where focused context delivered a ๐Ÿฎ.๐Ÿญ๐Ÿฑ๐˜… ๐—ถ๐—บ๐—ฝ๐—ฟ๐—ผ๐˜ƒ๐—ฒ๐—บ๐—ฒ๐—ป๐˜. The mindset shift: metadata was built for humans to browse. Now it also needs to work for machines to reason. Most teams are still optimizing for readability, not machine usability. If your "talk to data" initiative is stalling, it might not be a model problem. It might be a context problem. Manoj breaks down what machine-usable context actually looks like โ€” and how to get started without rebuilding your stack. Read it in Metadata Weekly: https://metadataweekly.substack.com/p/the-context-problem-nobodys-fixing