<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Anomaly-Detection on EnRedAndo Me - Carlos Prados</title><link>https://carlos.enredando.me/tags/anomaly-detection/</link><description>Recent content in Anomaly-Detection on EnRedAndo Me - Carlos Prados</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>mail@carlosprados.com (Carlos Prados)</managingEditor><webMaster>mail@carlosprados.com (Carlos Prados)</webMaster><copyright>© 2026 Carlos Prados</copyright><lastBuildDate>Fri, 31 Jul 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://carlos.enredando.me/tags/anomaly-detection/index.xml" rel="self" type="application/rss+xml"/><item><title>Four Silent Failures From Putting Models in the Data Path</title><link>https://carlos.enredando.me/posts/models-in-the-data-path/</link><pubDate>Fri, 31 Jul 2026 09:00:00 +0200</pubDate><author>mail@carlosprados.com (Carlos Prados)</author><guid>https://carlos.enredando.me/posts/models-in-the-data-path/</guid><description>&lt;p&gt;I assumed the models would be the hard part. They weren&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;For the last few months I&amp;rsquo;ve been building a suite of inference services that score data
inline as it arrives: models trained from data the system already collected, scoring on
the way in, the verdict landing as ordinary fields next to the measurement. Not an API
you call beside the pipeline — inside it. On CPU, milliseconds per document, which is
what makes the arrangement thinkable at all.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://carlos.enredando.me/posts/models-in-the-data-path/featured.jpg"/></item></channel></rss>