<?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 Arvind Sharma on Medium]]></title>
        <description><![CDATA[Stories by Arvind Sharma on Medium]]></description>
        <link>https://medium.com/@starkarvind1?source=rss-d912e7a92db5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pp4rTEU93GLLSBvB8H_B2g.jpeg</url>
            <title>Stories by Arvind Sharma on Medium</title>
            <link>https://medium.com/@starkarvind1?source=rss-d912e7a92db5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 15:15:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@starkarvind1/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[Git and Github: A comprehensive guide, shortcuts and some best practices]]></title>
            <link>https://medium.com/@starkarvind1/git-and-github-a-comprehensive-guide-shortcuts-and-some-best-practices-83c6a9edb936?source=rss-d912e7a92db5------2</link>
            <guid isPermaLink="false">https://medium.com/p/83c6a9edb936</guid>
            <category><![CDATA[git-and-github]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[git-commands]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Arvind Sharma]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 22:11:00 GMT</pubDate>
            <atom:updated>2025-01-12T22:11:00.748Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Everyone ! I’m <a href="https://www.linkedin.com/in/arvind-sharma-3884a2205/"><strong>Arvind Sharma</strong></a>, a third-year Computer Science Engineering student at NIT Bhopal. I am an upcoming SWE Intern at Google and a former intern at Alchemyst AI.</p><p>In this Blog, We <a href="https://www.linkedin.com/in/arvind-sharma-3884a2205/">Arvind Sharma</a> &amp; <a href="https://www.linkedin.com/in/dishatimbadiya/">Disha Timbadiya</a> are going to share a “comprehensive guide to Git and GitHub”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*aFgioBgW2TsFqo7duCfmIw.jpeg" /></figure><h3>What is Git and Why do we use it?</h3><p>Let’s first understand why do we need a software like git</p><p>Suppose you are working on a big project in a team which is in different parts of the world. Now how will you manage the codebase written by different team members, suppose guy1 made some changes in the code now he has to share the whole big package to everyone. And everyone will work on this new package now. And this will continue on small-small changes done by different team members.</p><p>Now think, how tiresome would it become?</p><p>So to resolve this issue we come up with a software called git and a platform called GitHub.</p><p>Now let’s understand what git and GitHub basically does. GitHub is a platform where all the projects can be put online and now these can be accessed by anyone whom you want to give access time to. And the codebase put on GitHub is called a repository or repo.</p><h3>What is Git?</h3><p>So basically git helps to interact with a GitHub repo from your system. Like accessing the repo and making changes in the codebase and reflecting it in the repo and much more. We will understand it all one by one in the blog ahead.</p><h3>Benefits of using git :</h3><ul><li>Pull Requests for Code Review: Owner needs to permit the change made by someone in the codebase, and it is called a pull request. If the change is valid and correct, the owner makes the pull request successful.</li><li>Commit History: You can see who had made what change in the past and it is called a commit.</li><li>Forking Repositories: You can fork any public repo and start working on it as your own repo.</li><li>Version Rewind: You can go back in time. Suppose you want the codebase the way it was 2 commits before, you can also do so.</li><li>Branching for Isolated Development: Git has a concept of branching. Suppose you are working on a app new feature which is used by the public. So what you can do is you can’t stop the main code working. You can start a branch apart from the main branch and implement the feature and if the feature is implemented successfully, you merge this branch with the main branch and now customers can use your new feature on the application.</li><li>Collaboration Without Overwriting Work: Multiple developers can work on the same codebase simultaneously without conflicting changes, features like branching and merging</li><li>Staging Area: Git provides a staging area where you can review and finalize changes before committing them, giving better control over what gets added to the repository.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/0*xPJ1u4YrFEpkv7rP" /></figure><h3>Basic Git Commands</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/0*gW9N3v-uVZl4iPSB.png" /></figure><h3>What is GitHub?</h3><p>GitHub is a web-based platform for hosting Git repositories. It enhances Git with collaboration tools, issue tracking, and CI/CD integration, making it an invaluable tool for teamwork and project management.</p><h3>Git vs. GitHub</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/795/0*gTsoW5oHzzasj3T_.png" /></figure><h3>Git Workflow Example:</h3><h3>1] Initialize a Git Repository:</h3><blockquote>git init</blockquote><h3>2] Add a File and Commit:</h3><h4>Create and add a new file:</h4><blockquote>echo “Hello, Git!” &gt; hello.txt</blockquote><h4>If file is already created</h4><blockquote>git add fileName.txt</blockquote><blockquote>git commit -m “Add fileName.txt file”</blockquote><h3>3] View the Commit History:</h3><blockquote>git log</blockquote><h3>Branching in Git:</h3><p>Branching allows developers to create isolated environments for developing features or fixing bugs without affecting the main codebase.</p><h3>Example</h3><h3>1] Create a new branch:</h3><blockquote>git branch feature-xyz<em> [</em>feature-xyz<em> : is the name of the branch]</em></blockquote><blockquote>git checkout feature-xyz</blockquote><h3>2] Work on the branch:</h3><blockquote>echo “New feature code” &gt; feature.txt</blockquote><blockquote>git add feature.txt</blockquote><blockquote>git commit -m “Add feature code”</blockquote><h3>3] Merge the branch:</h3><blockquote>git checkout main</blockquote><blockquote>git merge feature-xyz</blockquote><h3>GitHub Workflow Example:</h3><h3>1] Create a Repository:</h3><ul><li>Go to GitHub and click on New Repository.</li><li>Add a name, description, and set the visibility (public or private).</li></ul><h3>2] Clone the Repository:</h3><blockquote>git clone &lt;<a href="https://github.com/username/repository.git">https://github.com/username/repository.git</a>&gt;</blockquote><ul><li>[You can get this link by opening the repository and clicking on the dark green button &lt;&gt; Code]</li></ul><h3>3] Make Changes:</h3><ul><li>Add, modify, or delete files in the repository.</li></ul><h3>4] Push Changes:</h3><blockquote>git add .</blockquote><p>[Adds all the changes to the staging area, one can also do individual files, ex — git add fileName.txt]</p><blockquote>git commit -m “Your commit message”</blockquote><blockquote>git push origin main</blockquote><h3>5] Create a Pull Request:</h3><ul><li>Open a pull request to propose changes.</li><li>Collaborators can review and merge the pull request.</li></ul><h3>Forking and Pull Requests on GitHub</h3><p>Forking allows you to create a copy of someone else’s repository, enabling independent development. Pull requests are used to propose and discuss changes to the original repository.</p><h3>STEPS:</h3><h3>1] Fork a Repository:</h3><ul><li>Click on the Fork button in the desired repository.</li></ul><h3>2] Clone Your Fork:</h3><blockquote>git clone <a href="https://github.com/your-username/forked-repo.git">https://github.com/your-username/forked-repo.git</a></blockquote><h3>2.0] Create new branch: [Recommended: one branch, one pull request]</h3><blockquote>git branch pull1</blockquote><blockquote>git checkout pull1</blockquote><h3>3] Make Changes and Push:</h3><blockquote>git add .</blockquote><blockquote>git commit -m “Update file”</blockquote><blockquote>git push origin pull1</blockquote><h3>4] Create a Pull Request:</h3><ol><li>Navigate to the original repository.</li><li>Click on Pull Requests &gt; New Pull Request.</li><li>Select your branch as the source and the original repository’s branch (e.g. main) as the target.</li><li>Add a description and submit.</li></ol><h3>Advanced Git Commands</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/0*6IFiUk44WoQ4UsUr.png" /></figure><h3>Git Stash</h3><ul><li>Git stash is a useful feature that temporarily saves your uncommitted changes without adding them to the repository.</li><li>It’s like a clipboard for your work, allowing you to switch branches or work on something else without losing progress. Later, you can apply the stashed changes back when needed using commands like:</li></ul><blockquote>git stash apply</blockquote><blockquote>git stash pop</blockquote><h3>Upstream</h3><ul><li>In Git, “upstream” typically refers to the main branch or the central repository you pull changes from or push changes to.</li><li>It’s a common term when working with remote repositories, indicating the source of truth for your project. Commands to interact with upstream branches:</li></ul><blockquote>git push origin main</blockquote><blockquote>git pull upstream</blockquote><h3>Unstaging a commit</h3><ul><li>If you want your previous code (some commits back), you can unstage your commits using the command</li></ul><blockquote>git reset &lt;commit-id&gt;</blockquote><p>[You can get the commit id from git log command, all commits before this will be removed]</p><blockquote>git reset -soft &lt;commit_id&gt;</blockquote><p>This command brings us back to a previous commit, but without discarding changes.</p><h3>Some shortcuts to keep in mind</h3><ol><li><strong><em>git add {regex}</em><br></strong>We can use regex without git add command. git add *.py [It will add all the files ending with .py]</li><li><strong><em>git checkout -b branchName</em>: </strong>This command creates new branch and switches to it.</li><li><strong>Always do git pull before working on a feature.</strong> To avoid merge conflicts as much as possible.</li><li><strong>One commit per task: </strong>We should avoid making our commit history messy and for that we should only have one commit per task. And to implement this use the following command:</li><li><strong><em>git commit — amend — no-edit</em></strong>: This command adds our latest changes into our latest commit without creating an entirely new commit.</li><li><strong><em>git log — oneline</em></strong><br>Displays the commit hash and commit message in a single line for each commit.<br>Very useful when you have to review back in your project having a lot of commits.</li></ol><h3>Commit Best Practices</h3><ol><li><strong>Commit Related Changes</strong>: Ensure each commit contains logically related changes.</li><li><strong>Commit Often</strong>: Frequent commits help avoid merge conflicts and maintain a clear history.</li><li><strong>Don’t Commit Half-Done Work</strong>: Use git stash for unfinished changes.</li><li><strong>Test Before Commit</strong>: Verify that the code works and has no side effects.</li><li><strong>Write Good Commit Messages</strong>: Summarize changes clearly and concisely.</li></ol><p>We hope this guide helps you understand and use Git and GitHub more effectively for your projects. Whether you’re just starting out or looking to improve your skills, these tools can make your work easier and more organized.</p><p>If you have any questions or feedback, feel free to reach out to us — we’d love to hear from you!</p><p><strong>Connect with us on LinkedIn:</strong></p><ul><li><a href="https://www.linkedin.com/in/arvind-sharma-3884a2205/">Arvind Sharma</a></li><li><a href="https://www.linkedin.com/in/dishatimbadiya/">Disha Timbadiya</a></li></ul><p>Happy coding! 😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83c6a9edb936" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google SWE Intern’25 Interview experience and Resources]]></title>
            <link>https://medium.com/@starkarvind1/google-swe-intern25-interview-experience-and-resources-10973cb48937?source=rss-d912e7a92db5------2</link>
            <guid isPermaLink="false">https://medium.com/p/10973cb48937</guid>
            <category><![CDATA[google-interview]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[intern]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Arvind Sharma]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 10:03:54 GMT</pubDate>
            <atom:updated>2025-01-12T22:06:48.588Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello, I am Arvind Sharma and I am currently pursuing my B. Tech in CSE at NIT Bhopal with an expected graduation year of 2026. In this article, I am going to share my interview experience for the Software Engineering Intern role at Google India’25.</p><p>I was very excited the first day Google came to my campus for hiring interns for 2025.</p><p>We had one OA round followed by 2 technical interview rounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kUHWbOtSyuDw5Gx_OT_DrA.png" /></figure><h3><strong>OA Round</strong></h3><p>There were two questions Of DSA. Both were like medium to hard leetcode questions. One was of 2-d DP. And the second one was of XOR.<br>If you are appearing for Google. You should master and practice questions on these topics — Binary Search, XOR, DP, Graph.</p><p>If you are having your OA or interview for Google within some weeks,<br>I recommend going through these questions first</p><p>1. <a href="https://www.geeksforgeeks.org/google-interview-questions/">https://www.geeksforgeeks.org/google-interview-questions/</a><br>2. <a href="https://takeuforward.org/interviews/strivers-sde-sheet-top-coding-interview-problems/">https://takeuforward.org/interviews/strivers-sde-sheet-top-coding-interview-problems/</a><br>3. <a href="https://leetcode.com/discuss/general-discussion/460599/blind-75-leetcode-questions">https://leetcode.com/discuss/general-discussion/460599/blind-75-leetcode-questions</a><br>Also, go through interview experiences of Google. For example: <a href="https://www.geeksforgeeks.org/software-engineer-interview-at-google-hyderabad">https://www.geeksforgeeks.org/software-engineer-interview-at-google-hyderabad</a> and related articles.</p><p>Use this as a benchmark for difficulty:</p><p><a href="https://leetcode.com/discuss/interview-experience?currentPage=1&amp;orderBy=newest_to_oldest&amp;query=Google">https://leetcode.com/discuss/interview-experience?currentPage=1&amp;orderBy=newest_to_oldest&amp;query=Google</a></p><p>To get an idea of OA questions, please see</p><p>1. <a href="https://leetcode.com/discuss/interview-question/352460/Google-Online-Assessment-Questions">https://leetcode.com/discuss/interview-question/352460/Google-Online-Assessment-Questions</a><br>2. <a href="https://leetcode.com/discuss/interview-question/1657574/Google-Internship-Question-2021-Finding-Arrays">https://leetcode.com/discuss/interview-question/1657574/Google-Internship-Question-2021-Finding-Arrays</a><br>3. <a href="https://leetcode.com/discuss/interview-question/469764/Google-Technical-Interview-Questions-or-Summer-Internship-or-2020">https://leetcode.com/discuss/interview-question/469764/Google-Technical-Interview-Questions-or-Summer-Internship-or-2020</a><br>4. <a href="https://leetcode.com/discuss/interview-question/794840/Google-or-Software-Engineer-Internship-2021-or-Online-test-questions-(OA)">https://leetcode.com/discuss/interview-question/794840/Google-or-Software-Engineer-Internship-2021-or-Online-test-questions-(OA)</a><br>5. <a href="https://leetcode.com/discuss/interview-question/1285431/Google-Interview-Questions">https://leetcode.com/discuss/interview-question/1285431/Google-Interview-Questions</a><br>6. <a href="https://leetcode.com/discuss/interview-question/1233715/Google-Interview-Questions-L3L4">https://leetcode.com/discuss/interview-question/1233715/Google-Interview-Questions-L3L4</a><br>7. <a href="https://leetcode.com/discuss/interview-question/2204105/Google-Interview-Questions">https://leetcode.com/discuss/interview-question/2204105/Google-Interview-Questions</a><br>8. <a href="https://leetcode.com/discuss/interview-question/1371222/Google-Questions">https://leetcode.com/discuss/interview-question/1371222/Google-Questions</a><br>9. <a href="https://leetcode.com/discuss/interview-question/794988/Google-SWE-Internship-2021-India-Online-Challenge">https://leetcode.com/discuss/interview-question/794988/Google-SWE-Internship-2021-India-Online-Challenge</a><br>10. <a href="https://leetcode.com/discuss/interview-question/927457/Google-or-OA-or-2021-SWE-Internship">https://leetcode.com/discuss/interview-question/927457/Google-or-OA-or-2021-SWE-Internship</a><br>11. <a href="https://leetcode.com/discuss/interview-question/1716993/Google-or-SWE-Internship-OA-or-Target-sum-but-no-target-given">https://leetcode.com/discuss/interview-question/1716993/Google-or-SWE-Internship-OA-or-Target-sum-but-no-target-given</a><br>12. <a href="https://leetcode.com/discuss/interview-question/2258398/GOOGLE-or-OA-or-2-Questions">https://leetcode.com/discuss/interview-question/2258398/GOOGLE-or-OA-or-2-Questions</a><br>13. <a href="https://leetcode.com/discuss/interview-question/549083/Google-Interview-2020-Internship">https://leetcode.com/discuss/interview-question/549083/Google-Interview-2020-Internship</a><br>14. <a href="https://leetcode.com/discuss/interview-question/818575/Google-India-or-SWE-Internship-2021-or-Online-Assessment">https://leetcode.com/discuss/interview-question/818575/Google-India-or-SWE-Internship-2021-or-Online-Assessment</a></p><p>After some days shortlisting came and my name was there. I was excited as well as little nervous as interview dates were after 2 days. <br>But I remained calm as I was preparing from 2 years. Preparation is what gives you confidence and calmness, so prepare hard.</p><h3>Interview Round 1</h3><p>The interviewer was cool and supportive, he asked me that I can call him with name if comfortable.<br>Then he asked me let’s discuss a question and he explained me the question and asked if I can build an approach to solve it and then write the code on the screen shared.</p><p>Firstly I thought brute force and discussed the approach with the interviewer. He asked me to implement it, In between he helped me at some points to choose the data structure and other discussions. So we implemented it in n3logn time complexity. It took me little more time as it was my first interview and took some time in figuring out the solution. Interviewer was not happy and he asked me Arvind we only have 15 mins, can you optimize this solution. Then I thought for some minutes and I found an optimization in the same approach and finally implemented it in n2 ✅.</p><p><strong><em>Tip — Practice mock interviews.</em></strong></p><h3>Interview Round 2</h3><p>In the second round, Interviewer introduced me with the process and we started with a tree question.<br>I thought for some minutes and got an approach using recursion + backtracking. I discussed the approach with the interviewer and then he asked me to implement it.<br>Then he did some follow ups and asked if I can optimize it further. And then I discussed with him an optimization approach using DP and implemented it.</p><p><strong><em>Tip — Communication is the key. Discuss your approach, questions and any help you need with the interviewer and create an interactive environment during the interview.</em></strong></p><p>And the next day I got the result. And it was like one of the best feelings of my life when I saw my name in the selection list. I was going to work in one of the top tech companies in the world and to learn and grow a lot with the people at Google. What can be the more super feeling than this. I called at home. And it was the best, happiest night of my life on which I couldn’t sleep but only thinking about the <strong><em>#lifeAtGoogle.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10973cb48937" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>