<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gcp on Samarthya</title><link>https://samarthya.me/tags/gcp/</link><description>Recent content in Gcp on Samarthya</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© Samarthya 2018-2026. All rights reserved.</copyright><lastBuildDate>Mon, 26 Oct 2026 18:10:00 -0400</lastBuildDate><atom:link href="https://samarthya.me/tags/gcp/index.xml" rel="self" type="application/rss+xml"/><item><title>AI in practice, part 2: ML pipelines on Google Vertex AI</title><link>https://samarthya.me/posts/ai-in-practice-2-vertex-ai-pipelines/</link><pubDate>Mon, 26 Oct 2026 18:10:00 -0400</pubDate><guid>https://samarthya.me/posts/ai-in-practice-2-vertex-ai-pipelines/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;&#10; A notebook that trains a good model once is an experiment. A pipeline that trains it again next week, on new&#10;data, and tells you whether it got better: that&amp;rsquo;s a system. Here&amp;rsquo;s how Google&amp;rsquo;s Vertex AI turns one into the other.&#10;&lt;/div&gt;&#10;&#10;&#10;&lt;h2 class="relative group"&gt;Why pipelines&#10; &lt;div id="why-pipelines" class="anchor"&gt;&lt;/div&gt;&#10; &#10; &lt;span&#10; class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;&#10; &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-pipelines" aria-label="Anchor"&gt;#&lt;/a&gt;&#10; &lt;/span&gt;&#10; &#10;&lt;/h2&gt;&#10;&lt;p&gt;Training a model is never one step. Data is extracted, cleaned and split; a model is trained, evaluated and&#10;compared with the current one; if it&amp;rsquo;s better, it&amp;rsquo;s registered and deployed. Done by hand in a notebook, that&#10;sequence is easy to get subtly wrong and impossible to audit.&lt;/p&gt;</description></item></channel></rss>