<?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 Rohan on Medium]]></title>
        <description><![CDATA[Stories by Rohan on Medium]]></description>
        <link>https://medium.com/@rd43403?source=rss-d2ed199d456c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*aU0LI53xonvFYdxF</url>
            <title>Stories by Rohan on Medium</title>
            <link>https://medium.com/@rd43403?source=rss-d2ed199d456c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:38:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rd43403/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[My Reflection on Linux and Bash]]></title>
            <link>https://medium.com/@rd43403/my-reflection-on-linux-and-bash-a2ecc3a113c0?source=rss-d2ed199d456c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2ecc3a113c0</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[bash]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[mindset-shift]]></category>
            <dc:creator><![CDATA[Rohan]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 03:40:13 GMT</pubDate>
            <atom:updated>2026-07-28T03:43:40.588Z</atom:updated>
            <content:encoded><![CDATA[<p>💡 One lesson has completely changed the way I approach learning.<br>For a long time, I believed that completing a course or following a tutorial meant I was learning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSRO1jsnh7yzBd85QMzt1Q.png" /></figure><p>Today, I see it differently.<br>🚀 Real learning begins when you start doing.<br>But an even bigger realization changed my perspective…<br>Before learning how to do something, I now try to understand why it exists in the first place.</p><p>🎯 I ask myself:<br>🔹 What problem was this task created to solve?<br>🔹 Why is this approach preferred over other alternatives?<br>🔹 How does each step contribute to solving the problem?<br>🔹 What would happen if this step didn’t exist?</p><p>Whether it’s ☁️ Cloud, ⚙️ DevOps, 🐧 Linux, 🤖 Automation, or any other technology, I’ve realized that understanding the purpose behind every command, configuration, or process makes learning far more meaningful.</p><p>🌱 What I’ve experienced:<br>✅ I remember concepts much longer.<br>✅ Troubleshooting becomes easier.<br>✅ I can connect ideas instead of memorizing commands.<br>✅ I become more confident applying knowledge in real-world scenarios.</p><p>I’ve noticed that once I understand the “WHY,” the “HOW” becomes much easier to remember — and applying it feels natural.<br>📌 This is the mindset I’ll carry into every project and every new technology I learn.</p><p>“Tell me and I forget. Teach me and I remember. Involve me and I learn.”<br>💭 Learning isn’t about completing tasks — it’s about understanding the problem, building the solution, and growing through the process.</p><p>P.S. This post is part of the DevOps Micro Internship (DMI) with Agentic AI — Cohort 3 — by <a href="https://www.linkedin.com/in/pravin-mishra-aws-trainer/">Pravin Mishra</a>. My graded progress is public: <a href="https://dmi.pravinmishra.com/s/rohandas98.html">https://dmi.pravinmishra.com/s/rohandas98.html</a></p><p>Start your DevOps journey: <a href="https://dmi.pravinmishra.com/?utm_source=student&amp;utm_medium=ps-blog&amp;utm_campaign=cohort3">https://dmi.pravinmishra.com/?utm_source=student&amp;utm_medium=ps-blog&amp;utm_campaign=cohort3</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2ecc3a113c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Reflection On Git and Github]]></title>
            <link>https://medium.com/@rd43403/my-reflection-on-git-and-github-aa495e4b06fa?source=rss-d2ed199d456c------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa495e4b06fa</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Rohan]]></dc:creator>
            <pubDate>Tue, 28 Jul 2026 03:35:15 GMT</pubDate>
            <atom:updated>2026-07-28T03:44:09.352Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9D6W9aqgdqrXxvXOJfuN9A.jpeg" /></figure><p>I started with the basics: initializing a local Git repository, understanding the importance of the .git folder, and configuring Git identity locally and globally.<br>Then I moved into real version-control practice: creating files, tracking changes, staging intentionally, writing meaningful commits, and checking history with git log.</p><p>One of the best parts was connecting Git practice with deployment. I deployed a static CodeTrack website on an EC2 instance using Nginx, which helped me understand how local changes become something users can actually access.<br>I also practiced a proper branching workflow by creating a feature branch for a Contact page, keeping changes isolated, verifying that the default branch stayed clean, and then merging after validation.</p><p>On GitHub, I learned how professional collaboration works: setting up a profile, forking repositories, cloning locally, configuring origin and upstream, syncing changes, pushing a branch, and opening a Pull Request.<br>The most valuable learning was building a Git safety net: a pre-commit hook to block risky commits and an AI-assisted /pr-ready review flow to analyze staged changes before opening a PR.</p><p>My key takeaway: DevOps is not only about tools. It is about disciplined workflows, clear history, safe collaboration, and human accountability.<br>Grateful to be learning through practical assignments in DMI Cohort 3.</p><p>P.S. This post is part of the DevOps Micro Internship (DMI) with Agentic AI — Cohort 3 — by <a href="https://www.linkedin.com/in/pravin-mishra-aws-trainer/">Pravin Mishra</a>. My graded progress is public: <a href="https://dmi.pravinmishra.com/s/rohandas98.html">https://dmi.pravinmishra.com/s/rohandas98.html</a>·</p><p>Start your DevOps journey: <a href="https://dmi.pravinmishra.com/?utm_source=student&amp;utm_medium=ps-blog&amp;utm_campaign=cohort3">https://dmi.pravinmishra.com/?utm_source=student&amp;utm_medium=ps-blog&amp;utm_campaign=cohort3</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa495e4b06fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Writing Code to Running the Cloud: How Rohan Kumar Das Became the Architect Behind the…]]></title>
            <link>https://medium.com/@rd43403/from-writing-code-to-running-the-cloud-how-rohan-kumar-das-became-the-architect-behind-the-7b49305a5780?source=rss-d2ed199d456c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b49305a5780</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[devops-training]]></category>
            <category><![CDATA[cloudarchitects]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Rohan]]></dc:creator>
            <pubDate>Thu, 02 Jul 2026 03:22:46 GMT</pubDate>
            <atom:updated>2026-07-02T03:22:46.431Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Writing Code to Running the Cloud: How Rohan Kumar Das Became the Architect Behind the Infrastructure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IbIXeIldyQMx7hzyfHpsyg.png" /></figure><p>Five years ago, Rohan Kumar Das was a developer shipping application code and quietly wondering why deployments still broke on Friday evenings. Today, he is the Cloud Architect other engineers call when a platform needs to scale — and the reason his company’s deployments haven’t broken in two years.</p><p>His pivot started in 2026, when he graduated from DMI Cohort 3 by Pravin Mishra — the program that gave his transition structure and direction. While still working as a developer, he went on to earn the AWS Solutions Architect Associate certification, and within a year had stacked the Certified Kubernetes Administrator (CKA) and HashiCorp Terraform Associate credentials on top of it, and moved into his first cloud engineering role. He later completed the AWS Solutions Architect Professional, the certification he called “the one that changed how I think, not just what I know.” Alongside the certifications, he worked through foundational books cover to cover — Designing Data-Intensive Applications and Computer Networking: A Top-Down Approach — building the systems and networking depth that separated him from engineers who only knew the tooling.</p><p>The proof, though, was never the paper. It was the work. He led the migration of his company’s legacy monolith to a containerized microservices platform on EKS, cutting infrastructure costs by 40% and reducing deployment time from hours to minutes. He designed the CI/CD pipelines that took his team from weekly releases to shipping multiple times a day.</p><p>Along the way, he published a technical blog, Pipelines &amp; Postmortems, where his write-ups on Kubernetes failure scenarios and cost-optimization patterns drew a steady readership of engineers facing the same problems he once did. He spoke at two regional DevOps meetups and mentored three junior developers through the same developer-to-cloud transition he made himself — one of whom now runs infrastructure at a fintech startup.</p><p>By 2031, Rohan led a platform engineering team of six, owning cloud architecture across three product lines. Asked what made the switch work, his answer was characteristically practical: “I stopped waiting to feel ready. I got certified, built things in public, and let the work speak.”</p><p>The work spoke. Loudly.</p><p><strong>P.S. This post is a part of DevOps Micro Internship with Agentic AI Cohort-3 by [Pravin Mishra](</strong>https://www.linkedin.com/in/pravin-mishra-aws-trainer/<strong>). You can start your DevOps journey by joining this [Discord community](</strong>https://discord.pravinmishra.com/<strong>) ( </strong><a href="https://discord.pravinmishra.com/"><strong>https://discord.pravinmishra.com/</strong></a><strong> ).</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b49305a5780" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>