<?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>Quality Assurance on Darshan Deshmukh</title><link>https://darshandeshmukh11.github.io/tags/quality-assurance/</link><description>Recent content in Quality Assurance on Darshan Deshmukh</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 02 Aug 2026 01:23:40 +0900</lastBuildDate><atom:link href="https://darshandeshmukh11.github.io/tags/quality-assurance/index.xml" rel="self" type="application/rss+xml"/><item><title>The Continuous Quality Platform</title><link>https://darshandeshmukh11.github.io/projects/continuos-quality-platform/</link><pubDate>Sun, 02 Aug 2026 01:23:40 +0900</pubDate><guid>https://darshandeshmukh11.github.io/projects/continuos-quality-platform/</guid><description>&lt;h1 id="the-continuous-quality-platform">The Continuous Quality Platform&lt;/h1>
&lt;p>&lt;strong>Building Quality Into the Developer Platform — Instead of Testing It at the End&lt;/strong>&lt;/p>
&lt;p>Over the years, while working with &lt;strong>startups and enterprise teams across different organizations&lt;/strong>, I&amp;rsquo;ve seen very different approaches to developer experience.&lt;/p>
&lt;p>Some teams invested early in strong developer platforms that made local development and testing almost effortless.&lt;/p>
&lt;p>Others chose not to invest much in local developer environments—often for a perfectly reasonable reason: &lt;strong>&amp;ldquo;We&amp;rsquo;re building an MVP. We need to show value to the business now, not spend weeks building internal tooling.&amp;rdquo;&lt;/strong>&lt;/p></description></item></channel></rss>