<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distills on Rohan Surve's personal homepage</title><link>https://rohansurve.com/blog/</link><description>Recent content in Distills on Rohan Surve's personal homepage</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 10 Sep 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://rohansurve.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>If a bug surfaces in production, who takes the blame?</title><link>https://rohansurve.com/blog/if-a-bug-surfaces-in-production-who-takes-the-blame/</link><pubDate>Wed, 10 Sep 2025 00:00:00 +0000</pubDate><guid>https://rohansurve.com/blog/if-a-bug-surfaces-in-production-who-takes-the-blame/</guid><description>&lt;p&gt;On World Tester&amp;rsquo;s Day, I looked at how our team at Sahi Pro handles product quality. If a bug surfaces in production, who takes the blame? Short Answer? We don&amp;rsquo;t focus on blame. We focus on fixing the issue and learning from it to make it future proof.
Here is our playbook:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Joint Ownership: We have a 1:1 developer-tester ratio. They work side-by-side, sharing ownership of features from start to finish. This is not just a process; it&amp;rsquo;s a wisdom nurtured and passed on top-down.&lt;/p&gt;</description></item><item><title>Webinar on challenges in Salesforce Test Automation</title><link>https://rohansurve.com/blog/webinar-on-challenges-in-salesforce-test-automation/</link><pubDate>Fri, 22 Aug 2025 00:00:00 +0000</pubDate><guid>https://rohansurve.com/blog/webinar-on-challenges-in-salesforce-test-automation/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;Focus on outcome, not output&lt;/strong&gt;&lt;/em&gt; appears rational yet difficult to comprehend. One common blocker to achieving outcomes is the mindset: &lt;em&gt;&lt;strong&gt;This is not part of my job profile&lt;/strong&gt;&lt;/em&gt;. This attitude is a hindrance to creating an impact hitherto an outcome.&lt;/p&gt;
&lt;p&gt;On August 21, my colleagues across departments (Marketing, QA, R &amp;amp; D, Sales) helped me deliver an online webinar on &lt;em&gt;Salesforce Test Automation using Sahi Pro&lt;/em&gt;. Many actively toiled in the background to make it happen. Be it the content, the lighting, the background settings, etc. everyone stepped up beyond their defined roles to make it happen. Some consciously choose to postpone certain decisions or meetings to ensure I had the space to focus.&lt;/p&gt;</description></item></channel></rss>