<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Embeddings on It Might be Working</title><link>https://iguessthatworks.com/tags/embeddings/</link><description>Recent content in Embeddings on It Might be Working</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Jeff Mayeur</copyright><lastBuildDate>Mon, 19 Oct 2026 07:00:00 -0700</lastBuildDate><atom:link href="https://iguessthatworks.com/tags/embeddings/index.xml" rel="self" type="application/rss+xml"/><item><title>From Plinko to Shape Sorter</title><link>https://iguessthatworks.com/posts/10-2026/mental/</link><pubDate>Mon, 19 Oct 2026 07:00:00 -0700</pubDate><guid>https://iguessthatworks.com/posts/10-2026/mental/</guid><description>
&lt;p&gt;In a recent conversation on these System One models I learned that my mental model for how to place them in my toolbox was way off. Even though that model correctly let me interpret them as a way to more efficiently classify requests, I'd missed the mark.&lt;/p&gt;
&lt;p&gt;The working structure I was using resembled a basic rules engine - an intentional Plinko - that would bucket a request based on the best fitting pattern. Functionally that's not entirely wrong, but where I was playing fast and loose was in the specificity of how queries would be classified - there's no ruleset doing the scoring - it's strictly embeddings producing a score that pinpoints the fastest answer.&lt;/p&gt;</description></item></channel></rss>