<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kunal Mankani on Medium]]></title>
        <description><![CDATA[Stories by Kunal Mankani on Medium]]></description>
        <link>https://medium.com/@mankani12?source=rss-aabe0cffaf94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*iePMT3MBb20O6UcuMIuHzg.png</url>
            <title>Stories by Kunal Mankani on Medium</title>
            <link>https://medium.com/@mankani12?source=rss-aabe0cffaf94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 22:44:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mankani12/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[MicroBlog: Why I want to transition into the so called trendy “Product Management role”]]></title>
            <link>https://medium.com/@mankani12/miniblog-why-i-want-to-transition-into-the-so-called-trendy-product-management-role-11c8ea7bb832?source=rss-aabe0cffaf94------2</link>
            <guid isPermaLink="false">https://medium.com/p/11c8ea7bb832</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Kunal Mankani]]></dc:creator>
            <pubDate>Mon, 04 Oct 2021 04:58:23 GMT</pubDate>
            <atom:updated>2021-10-04T12:31:43.618Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>Am I gonna be just a sophisticated email router?</em></strong> 😂😂</p><p>I never even knew that a role like Product Management existed even till working for a couple of years as an Engineer at different firms, because I never worked with one, and never had the chance to interact with such a position.</p><p>But when I actually came in contact with one of the Product Managers while working for a mid-sized Oregon based SaaS company, I realised how a PM really impacts the whole of the product lifecycle and is literally a translator from software building and operations teams to upper level strata of management including executives and board members.</p><p>Before understanding why I want to transition, I would like to give a debrief about my current role, I’m a senior cloud SRE at India’s largest E-commerce platform, where I have been actively involved in implementing a variety of cloud platform architectures for different product teams, who basically are our customers internally. Working in this role was what set a trigger to my aspirations for the product profile.</p><p>Jumping back a couple of years, I think it was back in college when I really loved understanding about the different products which had just popped up in the very immature yet rapidly evolving Indian startup ecosystem. I loved reading more about these product offerings, trying to grasp the nooks and corners of the functionality, and how the backend really works, I always used to wonder how enthralling it must be while working on such appalling ideas and taking them from plan to execution, but since I had no clue what Product Management was, I thought of this as more of a VP or Directorial role.</p><p>But luckily due to a number of reasons, India getting nurtured into its own Silicon Valley and tending to evolve into a truly great Product nation, we are changing the very definitions and hacking product growth like never before.<br>And, that’s what fueled me further into getting into a role propelling the growth of the very hub and spoke around which the wheel of any company rotates.</p><p>Feel free to connect with me over Linkedin to talk more about Product: <a href="https://www.linkedin.com/in/coderinprogress/">https://www.linkedin.com/in/coderinprogress/</a></p><p>Would love to chat and be of help in your product journey too. :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11c8ea7bb832" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The story of chaos and my love ❤️ for it — A dig at Chaos Engineering — Part 1]]></title>
            <link>https://medium.com/@mankani12/the-story-of-chaos-and-my-love-%EF%B8%8F-for-it-a-dig-at-chaos-engineering-part-1-c3e336cc8220?source=rss-aabe0cffaf94------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3e336cc8220</guid>
            <dc:creator><![CDATA[Kunal Mankani]]></dc:creator>
            <pubDate>Thu, 30 Jul 2020 23:23:16 GMT</pubDate>
            <atom:updated>2020-07-30T23:23:16.911Z</atom:updated>
            <content:encoded><![CDATA[<h3>The story of chaos and my love ❤️ for it — A dig at Chaos Engineering — Part 1</h3><p>I remember the first time I had heard about chaos in a Thermodynamics class, while trying to understand about <a href="https://www.merriam-webster.com/dictionary/entropy">Entropy</a>, that’s when I got a more practical and consistent real-life like context about “<strong>Chaos</strong>”, and it’s undeniable existence.</p><p>As per Wikipedia, the formal definition (just for a detailed scribble) :</p><blockquote>Chaos is the property of a complex system whose behaviour is so unpredictable as to appear random, owing to great sensitivity to small changes in conditions.</blockquote><p>It’s almost in plain English without any jargon, so I would expect you to pretty much get the point of it, but just for the fun of it let’s do some movie reference — It’s a story about a little girl, who reminds her Astronomer dad of Murphy’s law when he gets a flat tyre (reference: Interstellar movie).</p><p>So Murphy’s law states that:</p><blockquote>Anything that can go wrong will go wrong.</blockquote><p>Same goes with software systems, especially because such a complex system has so many vulnerabilities and points of failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vrCiR3RtBJtSWK4rFFKhXQ.png" /></figure><p>Much about definitions, let’s get to the point of how did I come in contact with Chaos as a Site Reliability engineer, what does it mean in the tech field, and it’s inculcation in modern-day engineering practices, and last but not the least my love for the notion.</p><p>A couple of months back, my team of SREs were given a task of initiating Chaos practices in the Marketplace team, to raise the standards of availability and reliability of customer facing products at Atlassian, which can be later vertically scaled to different product silos.</p><p>I started reading about it on how do firms use and apply the concept to their products or services they provide and how Netflix got the tools right to begin with in the form of <a href="https://netflix.github.io/chaosmonkey/">Chaos-Monkey</a>.</p><p>Too much talk, so what the heck Chaos engineering really is? Don’t go around googling yet, let me first explain you in a sense a 3rd grader would grasp this. Heard of Divide and Conquer? Let’s split up the words!!</p><p>“Chaos” means breaking, tearing and wearing down something tangible, but wait, software or an application isn’t really tangible, it’s something on the computer (remember we’re talking to a kid here), well, yes a software is within the computer as you see it, but it is actually hosted somewhere on another computer(cloud or server), which is a physical device right? That too, a physical device is hosted in a location, and ultimately it’s still a computer, and a computer which has to fall under a lot of load due to people requesting access to the application hosted on them, so a hardworking computer, hence it is bound to fail at some point of time in a physical or logical manner.<br>Engineering is when we come up with traditional or non-traditional ways of fixing a problem, so there you go!</p><p>So, I’ve fed you the sweet parts, let’s crunch with some technical details. Since a lot of parts of Chaos Engineering at Atlassian were custom, I will only present the relevant information.</p><h3>Implementing the concept:</h3><p>There were a couple of things which had to be in place before the implementation — Yes, the planning phase.</p><p>For planning purposes, the team was setup such that all the people associated with the service were to be included in the planning meet. We followed a YBIYRI model, which stands for <strong><em>You Build It, You Run It</em></strong>. This places the developers under direct responsibility for any service and its maintenance which they design and engineer.</p><p>The team consisted of all the developers for the service, SREs(myself included), and an SME(Subject Matter Expert) or an Architect sometimes.<br>I prepared a draft which had all the elements of the experiment, including timestamps of every event, setting up the alert flow system using SignalFx, using Terraform to allocate AWS resources of our infrastructure to create detectors and dashboards based on different kinds of events which would be triggered throughout the experiment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3e336cc8220" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>