<?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 Muhammad Arsalan Badar on Medium]]></title>
        <description><![CDATA[Stories by Muhammad Arsalan Badar on Medium]]></description>
        <link>https://medium.com/@mbadar?source=rss-203592535d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TulUHUA9hAiOLZnUAGCcow@2x.jpeg</url>
            <title>Stories by Muhammad Arsalan Badar on Medium</title>
            <link>https://medium.com/@mbadar?source=rss-203592535d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:16:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mbadar/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[Never be afraid of making bold changes]]></title>
            <link>https://medium.com/@mbadar/never-be-afraid-of-making-bold-changes-8bb144e143d1?source=rss-203592535d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bb144e143d1</guid>
            <category><![CDATA[bold]]></category>
            <category><![CDATA[initiative]]></category>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[fear-of-failure]]></category>
            <category><![CDATA[passionate]]></category>
            <dc:creator><![CDATA[Muhammad Arsalan Badar]]></dc:creator>
            <pubDate>Mon, 31 Aug 2020 15:21:41 GMT</pubDate>
            <atom:updated>2020-08-31T16:06:54.506Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4UCqYOfI8_98Lb23GdZTeA.jpeg" /></figure><p>Over the last five years in the software industry, I have witnessed (and experienced) the anxiety that developers have when suggesting and implementing code changes to improve the way teams work.</p><p>Even if it is apparent that these changes will benefit everyone, the sentiment is generally a feeling of hesitation — to take ownership, to take initiative, and to see the execution through till the end.</p><p>One of the most vital aspects that can enable making bold changes is the company’s culture. An encouraging company culture makes employees feel more comfortable, and helps bring down invisible boundaries that would otherwise hold them back.</p><p>That being said, it is still up to us on an individual level to start taking ownership and be bolder in suggesting changes to our colleagues.</p><p>Up until last year, I was in exactly such a situation. Due to a lack of experience and tenure in the industry, I was hesitant to take ownership of initiatives that will change the way teams work. I was afraid of pushback from my team and of course the fear of failing.</p><p>Pushback normally comes out of concerns the team might have. Intuit, the company I work for, has an incredibly inspiring and encouraging culture and work environment. Intuit encourages its employees to fail fast and learn iteratively.</p><p>Despite this, there was still a lingering fear that held me back.</p><p><strong>My story</strong></p><p>Here’s some context: a project I was working on was approximately 15+ years old monolith Java application with no code formatting rules. Everyone was using their own formatting settings from IntelliJ IDE.</p><p>There were tons of issues, which really bothered me and my peers felt the same way too. A few highlights from the situation:</p><ul><li>Working on an existing class means there will be a difference in formatting.</li><li>If auto-format on save action is enabled, it shows the full file as changed, making it harder to perform code review.</li><li>Some files used different line endings, and updating these files shows changes in the whole file, making it harder to review.</li></ul><p>After working on that code for around 7 months, I realized we needed to have a general formatting guideline. I shared this idea with the team, who in turn shared concerns about losing the code history</p><p>Let’s say someone is updating only one line and running the formatter. It will update the full file and replace the code history. So I dropped that idea.</p><p>After a couple of weeks, I saw the same problem again in multiple pull requests. I discussed this issue again, this time making sure to include senior developers in the meeting, and then proposed a strategy of making the changes under one commit. Some developers were open to this idea, but we never moved on to actually discussing timelines for implementation.</p><p>A moment of inspiration and encouragement was all I needed from a colleague to take the next step: documenting the approach, taking full ownership of the task, and presenting it back to the team.</p><p>The team was hesitant at first, wanting to ensure this change would not break anything as the changes were hard to review.The codebase already had an acceptable amount of unit testing and integration testing coverage, but there was always a possibility of something breaking due to edge cases that tests did not cover.</p><p>Here is the snapshot of pull request changes in github:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/0*TBn6V04AH0gX66EZ" /></figure><p>To tackle that, I made the required changes, deployed to one of our test environments, tested both manually and via automation tests, and shared the results with the team.</p><p>The next step was merging the changes, and in order to do that I had to make sure that I checked off the following things:</p><ol><li>All developers knew everything about what had changed</li><li>All open pull requests would have to be merged before changes were implemented</li><li>We would have ample resource capacity to help with resolving the conflicts</li></ol><p>The support I needed came in the form of positive comments and encouragement from both my colleagues and my manager. The confidence I needed to push this through was the differentiating factor. I found it much easier to convince stakeholders once I alleviated the anxiety and fear of breaking code by employing tests and safeguards.</p><p><strong>Final thoughts</strong></p><p>Even though it took 2 months to execute this project from start to finish, I was committed to seeing it through to the very end in order to prove the importance of taking such steps to myself. The additional boost was from the empowering confidence my team members gave me.</p><p>Some very valuable takeaways from my journey:</p><ul><li>Present your ideas clearly and take ownership of other related tasks as well</li><li>Even if you don’t have an incentive to take the initiative, just do it. It will benefit the teams in the longer run.</li><li>If you fail, you still end up learning something new</li><li>Learning means improving, so you’re now a better version of yourself</li></ul><p>Here are some principles I followed to get this initiative off the ground:</p><ul><li>Analyze the problem, and validate if it is actually a problem</li><li>Identify the key stakeholders related to the problem</li><li>Think about solutions, weigh in all the alternatives, and document all positives and negatives of all possible solutions</li><li>Document the impacts of all possible solutions</li><li>Pick the most ideal solution, perform a Proof of Concept, and share your learnings</li><li>Execute the plan and take help from team members as needed</li></ul><p>Finally, if you keep all of your ideas to yourself and never share your thoughts, you’ll only be restricting your own innovation and growth. Sharing your thoughts always helps you to validate and get more ideas from the pointers you will get from others. So never be afraid of making bold changes. First time you will be hesitant and uncomfortable, but moving forward, it will boost up your confidence level as it did for myself!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bb144e143d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>