<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on</title><link>https://lab.extrai.it/en/tags/automation/</link><description>Recent content in Automation on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026</copyright><lastBuildDate>Tue, 10 Mar 2026 16:43:20 +0000</lastBuildDate><atom:link href="https://lab.extrai.it/en/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Pipeline Eval Strategies</title><link>https://lab.extrai.it/en/posts/pipeline-eval-strategies/</link><pubDate>Tue, 10 Mar 2026 16:43:20 +0000</pubDate><guid>https://lab.extrai.it/en/posts/pipeline-eval-strategies/</guid><description>&lt;p&gt;Here&amp;rsquo;s how the story often goes: you have this process at your company that absolutely has to be done — processing claims, triaging requests, reviewing documents — that kind of task that requires a human, but everyone involved would rather spend their time self-inflicting mild electric shocks as in that famous experiment about boredom rather than actually doing it, and you know that if you could just take it off people&amp;rsquo;s plates, the whole team would be better for it and get you a nice present. So you think &amp;ldquo;but wait, AI is all over the place today&amp;rdquo; and you decide to give it a try.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://lab.extrai.it/en/posts/pipeline-eval-strategies/featured.en.jpg"/></item></channel></rss>