<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Yash Kamothi</title><link>https://yash-kamothi.com/posts/</link><description>Recent content in Posts on Yash Kamothi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 13 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yash-kamothi.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Needing a Hero Is a Warning Sign</title><link>https://yash-kamothi.com/posts/needing-a-hero/</link><pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate><guid>https://yash-kamothi.com/posts/needing-a-hero/</guid><description>&lt;p>Needing a hero in your organization is a warning sign, unless you&amp;rsquo;re Disney or Marvel of course.
However, at any company, it&amp;rsquo;s a red flag, because it means there are layers of failures, many of them silent and undetected for a long time.&lt;/p>
&lt;p>I say this while actually being that hero recently at Sidecar Health.
We had a legacy ETL pipeline that had been silently failing for 6 months and no one knew.
A vendor drops provider data into our SFTP, and we are supposed to ingest it, validate it, and update internal models.
This data is customer-facing and valued by our executives, which makes it even harder to reckon with how long it had gone unnoticed.
Now I finally know the answer to the age-old question: when a tree falls in the forest and no one is around to hear it, it does &lt;strong>not&lt;/strong> make a noise.&lt;/p></description></item></channel></rss>