<?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 Abhinav on Medium]]></title>
        <description><![CDATA[Stories by Abhinav on Medium]]></description>
        <link>https://medium.com/@abhinav1712003?source=rss-ae6091faa7b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*S7ON7hjJJ9EOV1Ki6DHUUw.jpeg</url>
            <title>Stories by Abhinav on Medium</title>
            <link>https://medium.com/@abhinav1712003?source=rss-ae6091faa7b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:51:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhinav1712003/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[Learning GitHub Collaboration and AI-Assisted Code Reviews in My DevOps Journey]]></title>
            <link>https://medium.com/@abhinav1712003/learning-github-collaboration-and-ai-assisted-code-reviews-in-my-devops-journey-8d8369b46a01?source=rss-ae6091faa7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d8369b46a01</guid>
            <category><![CDATA[devops-training]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Abhinav]]></dc:creator>
            <pubDate>Fri, 24 Jul 2026 12:35:03 GMT</pubDate>
            <atom:updated>2026-07-24T12:35:03.603Z</atom:updated>
            <content:encoded><![CDATA[<p>Every week in my DevOps learning journey teaches me something new, and this week’s assignment was one of the most interesting so far. Instead of only learning Git commands, I got to experience how developers actually collaborate on projects and how AI can help review code without taking control.</p><p>Before this assignment, I knew the basic Git commands like git add, git commit, and git push. But I didn&#39;t fully understand why developers use branches, forks, or Pull Requests. After completing this project, those concepts became much clearer.</p><h3>Working with Git and GitHub</h3><p>The first part of the assignment focused on collaboration using GitHub.</p><p>I started by forking a repository and cloning it to my computer. Then I created a separate feature branch instead of working directly on the main branch.</p><p>At first, I wondered why this extra step was necessary. Later, I understood that using a feature branch keeps the main branch safe and makes it easier to review changes before merging them.</p><p>I also learned how to keep my fork updated with the original repository. This helped me understand how developers stay in sync when many people are working on the same project.</p><p>Finally, I made my changes and created a Pull Request. Although my changes were small, the complete workflow showed me how real teams collaborate on software projects.</p><h3>Building a Git Pre-Commit Hook</h3><p>The second part of the assignment introduced Git hooks.</p><p>I created a pre-commit hook that checks files before a commit is created. To test it, I added a fake AWS access key and a debug statement to my code.</p><p>When I tried to commit, the hook immediately blocked it.</p><p>This showed me how Git hooks can help catch simple mistakes before they reach the repository. It was interesting to see that a small script can improve code quality and security.</p><h3>Using AI to Review Changes</h3><p>Another exciting part of this assignment was using <strong>Claude Code</strong> with a custom /pr-ready skill.</p><p>Instead of changing my files automatically, Claude reviewed my code and gave suggestions.</p><p>It detected the hardcoded key, pointed out the debug statement, suggested improvements, and even drafted a Pull Request title and description.</p><p>I still had to review everything before using it, which I think is the right approach.</p><h3>What I Learned About AI</h3><p>The biggest lesson for me wasn’t about Git.</p><p>It was about how AI should be used.</p><p>Before this assignment, I thought AI should automatically fix problems and perform actions.</p><p>Now I understand that AI is much more useful when it helps us analyze our work, points out mistakes, and gives suggestions. The final decision should always remain with the developer.</p><p>That makes the workflow much safer and more reliable.</p><h3>Final Thoughts</h3><p>This assignment gave me practical experience with GitHub collaboration, Git hooks, and AI-assisted code reviews.</p><p>More importantly, it helped me understand <strong>why</strong> these tools exist instead of simply teaching me the commands.</p><p>I’m still a beginner, but every assignment helps me become a little more confident with Git, GitHub, Linux, and DevOps.</p><p>Step by step, I’m learning how real software development teams work, and that’s what makes this journey exciting.</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/YOUR-GITHUB-USERNAME.html">https://dmi.pravinmishra.com/s/</a><a href="https://github.com/abhinavleo/devops-micro-internship-pravinmishra/commits?author=abhinavleo">abhinavleo</a><a href="https://dmi.pravinmishra.com/s/YOUR-GITHUB-USERNAME.html">.html</a> · 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=8d8369b46a01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience Completing the DevOps Micro Internship Pre-Entry Assessment]]></title>
            <link>https://medium.com/@abhinav1712003/my-experience-completing-the-devops-micro-internship-pre-entry-assessment-7f58771d5c56?source=rss-ae6091faa7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f58771d5c56</guid>
            <category><![CDATA[cohort-3]]></category>
            <category><![CDATA[idm]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Abhinav]]></dc:creator>
            <pubDate>Fri, 24 Jul 2026 12:29:47 GMT</pubDate>
            <atom:updated>2026-07-24T12:29:47.435Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started the pre-entry assessment for the <strong>DevOps Micro Internship</strong>, I thought it would only be about answering a few questions. After completing it, I realized it was designed to help me understand the basic concepts that every DevOps learner should know before moving on to bigger projects.</p><p>One of the first things I practiced was using <strong>ChatGPT</strong> to ask better questions. I learned that the way we ask a question can change the quality of the answer. Instead of asking very broad questions, I tried writing simple and specific prompts. This made it much easier to understand topics like networking and protocols.</p><p>Next, I learned about <strong>DNS (Domain Name System)</strong>. Before this, I only knew that typing a website name opened a webpage. Now I understand that DNS works like a phonebook for the internet. It converts a domain name into an IP address so that computers know where to find a website. I also learned about <strong>A Records</strong>, which connect a domain directly to an IPv4 address.</p><p>Another topic I explored was <strong>application architecture</strong>. I understood the difference between a <strong>two-tier</strong> and a <strong>three-tier</strong> application. A two-tier application usually has the frontend connected directly to the database, while a three-tier application includes a backend between the frontend and the database. I also became familiar with the technologies used in each layer, such as HTML, CSS, JavaScript, React, Node.js, Python, MySQL, and PostgreSQL.</p><p>I also spent some time learning about different <strong>DNS record types</strong>. I learned that:</p><ul><li><strong>A Record</strong> connects a domain to an IPv4 address.</li><li><strong>CNAME Record</strong> points one domain to another domain.</li><li><strong>MX Record</strong> is used for email services.</li></ul><p>These concepts were new to me, but after reading and practicing, they became much easier to understand.</p><p>Another part of the assessment was setting up <strong>Visual Studio Code</strong> and using the terminal. I customized VS Code and practiced basic commands like pwd, ls, and dir. At first, using the terminal felt a little unfamiliar, but after trying the commands a few times, I became more comfortable navigating folders and files.</p><p>The biggest lesson I learned from this assessment is that strong fundamentals are very important. Before learning cloud platforms, automation, or CI/CD, it is necessary to understand networking, DNS, application architecture, and basic development tools. These topics may seem simple, but they are the building blocks of DevOps.</p><p>I also realized that learning becomes much easier when I practice instead of just reading. Every small task gave me more confidence, and I now feel better prepared for the upcoming DevOps assignments.</p><p>This assessment was a great starting point for my DevOps journey. I still have a lot to learn, but it helped me build a solid foundation and motivated me to keep improving step by step. I’m looking forward to learning Linux, Git, Docker, Kubernetes, AWS, and many other DevOps tools in the coming weeks.</p><p>Thank you to <strong>Pravin Mishra</strong> and the mentors for creating a practical learning experience that focuses on understanding concepts instead of simply memorizing them. I’m excited to continue this journey and keep sharing what I learn along the way.</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/YOUR-GITHUB-USERNAME.html">https://dmi.pravinmishra.com/s/</a><a href="https://github.com/abhinavleo/devops-micro-internship-pravinmishra/commits?author=abhinavleo">abhinavleo</a><a href="https://dmi.pravinmishra.com/s/YOUR-GITHUB-USERNAME.html">.html</a> · 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=7f58771d5c56" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building My First AI-Assisted Linux Health Check Workflow]]></title>
            <link>https://medium.com/@abhinav1712003/building-my-first-ai-assisted-linux-health-check-workflow-9d0992f0658c?source=rss-ae6091faa7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d0992f0658c</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[bash-script]]></category>
            <category><![CDATA[claude]]></category>
            <dc:creator><![CDATA[Abhinav]]></dc:creator>
            <pubDate>Fri, 17 Jul 2026 16:59:51 GMT</pubDate>
            <atom:updated>2026-07-17T16:59:51.419Z</atom:updated>
            <content:encoded><![CDATA[<h4>P.S. This post is part of the DevOps Micro Internship with Agentic AI Cohort 3 by Pravin Mishra (<a href="https://www.linkedin.com/in/pravin-mishra-aws-trainer/">https://www.linkedin.com/in/pravin-mishra-aws-trainer/</a>). You can begin your DevOps journey by joining the DMI waiting list (<a href="https://forms.gle/3hvrWJBDzsDeJoPs6">https://forms.gle/3hvrWJBDzsDeJoPs6</a>).</h4><p>This week was one of the most interesting weeks in my DevOps learning journey.</p><p>Before this assignment, I always thought AI should solve problems automatically. But after completing this project, I understood that AI is more useful when it helps us find the problem, and then a person decides how to fix it.</p><p>During the DevOps Micro Internship, I have learned many things like Linux, Bash scripting, AWS, Nginx, and application deployment. In this assignment, I got the chance to use all these skills together in one project.</p><h3>What I Built</h3><p>I created a Linux health check script using Bash.</p><p>Instead of running many Linux commands one by one, the script checks the server automatically and collects important information in one report.</p><p>It checks things like:</p><ul><li>Nginx service status</li><li>HTTP response</li><li>Port 80</li><li>Memory usage</li><li>Disk usage</li></ul><p>This makes checking the server much faster and easier.</p><h3>Using AI with the Health Check</h3><p>After the Bash script collected the server information, I connected it with a Claude Code skill.</p><p>Claude did not change anything on the server.</p><p>It only read the report, explained the problem, and suggested the next step.</p><p>I liked this because AI was helping me understand the issue instead of making changes by itself.</p><h3>Testing the Workflow</h3><p>To test everything, I stopped the Nginx service on purpose.</p><p>When I ran the health check script, it found that:</p><ul><li>Nginx was not running.</li><li>Port 80 was not listening.</li><li>The website was not responding.</li></ul><p>Claude looked at the report and suggested starting the Nginx service.</p><p>Instead of doing it automatically, I checked the suggestion and then started Nginx myself.</p><p>After that, I ran the health check again, and the report showed that everything was working normally.</p><h3>What I Learned</h3><p>While working on this assignment, I also made a few mistakes in my Bash scripts. Sometimes I used the wrong command or missed a small detail. I spent time fixing those mistakes, and that helped me understand Linux and Bash much better.</p><p>The biggest lesson I learned is that we should never guess when something goes wrong.</p><p>First, collect the information.</p><p>Then understand the problem.</p><p>After that, fix it.</p><p>Finally, check again to make sure everything is working.</p><p>I also learned that AI should not automatically make changes to a production server. It is better when AI helps with the analysis, while a human reviews the information and decides what action to take.</p><h3>Final Thoughts</h3><p>This assignment was more than just writing Bash scripts. It showed me how Linux, Bash, and AI can work together to make troubleshooting easier and safer.</p><p>Every assignment in this internship is helping me improve my Linux, Bash, AWS, and DevOps knowledge. I still have a lot to learn, but I feel more confident after completing each project.</p><p>Step by step, I am learning how to solve real problems instead of just running commands, and that is what makes this journey exciting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d0992f0658c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflection — Week 2]]></title>
            <link>https://medium.com/@abhinav1712003/reflection-week-2-cf9b4b13d2c5?source=rss-ae6091faa7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf9b4b13d2c5</guid>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[claude]]></category>
            <dc:creator><![CDATA[Abhinav]]></dc:creator>
            <pubDate>Fri, 10 Jul 2026 09:13:50 GMT</pubDate>
            <atom:updated>2026-07-28T15:12:48.699Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*ipfs2938SU7fj17gYr-Psg.png" /></figure><p>When I started this week, I expected to learn a few new AI features and move on. Instead, I ended up changing the way I think about using AI while learning DevOps.</p><p>Before this course, I mostly used AI whenever I got stuck. I would ask a question, copy the answer if it worked, and continue with my work. I never thought about how AI could become part of my workflow instead of just being a tool for quick answers.</p><p>This week was different because I spent more time inside Claude Code than simply chatting with an AI. I learned that AI is much more useful when it understands the project, follows instructions, and works within clear boundaries. Features like project memory, permissions, hooks, and skills were completely new to me, so there was a lot to learn.</p><p>The biggest lesson didn’t come from watching the course videos. It came from making mistakes.</p><p>One issue I remember clearly was while setting up hooks. I kept getting an error saying the post-tool-logger.sh file could not be found. At first, I thought something was wrong with Claude Code itself. I spent quite a while trying different fixes before I realized the problem was in my own project setup. Once I corrected it, everything worked as expected. It reminded me that the first error message isn’t always the real problem, and patience is often more important than speed.</p><p>I also ran into another issue while following the Terraform exercises. I expected every command shown in the course to work exactly the same on my computer. When they didn’t, I had to read the documentation, check the project files, and understand what had changed instead of blindly repeating commands. That experience taught me that technology changes, and learning how to investigate is more valuable than memorizing steps.</p><p>Another thing that stood out was project memory. Before this week, I thought every new AI conversation meant explaining my project from the beginning again. After learning how Claude Code stores project instructions, I understood why documentation matters. Instead of repeating everything, I can give the AI a clear understanding of the project once and continue building from there. It makes working with AI feel much more organized.</p><p>This week also changed how I think about AI itself. Earlier, I believed AI usually had the correct answer. Now I see it differently. AI can save time, explain concepts, and generate ideas, but it cannot replace my responsibility as the developer. I still need to test commands, verify outputs, and understand why something works before I trust it.</p><p>Personally, I also learned something about myself. Whenever I see an error, my first reaction is to fix it as quickly as possible. This week made me realize that slowing down often solves problems faster. Reading logs carefully, checking documentation, and understanding the cause usually works better than trying random solutions.</p><p>Going forward, I want to build one simple habit. Whenever I solve a problem, I will write down not only the solution but also the reason the problem happened. I think this will help me remember the lesson and make troubleshooting easier in future projects.</p><p>Overall, Week 2 was not just about learning new AI features. It taught me to think more like an engineer. Instead of looking for the fastest answer, I want to understand the problem, test different approaches, and build better habits as I continue my DevOps journey.</p><blockquote><em>P.S. This post is part of the DevOps Micro Internship (DMI) with Agentic AI — Cohort 3 — by </em><a href="https://www.linkedin.com/in/pravin-mishra-aws-trainer/"><em>Pravin Mishra</em></a><em>. My graded progress is public: </em><a href="https://dmi.pravinmishra.com/s/YOUR-GITHUB-USERNAME.html"><em>https://dmi.pravinmishra.com/s/</em></a><a href="https://github.com/abhinavleo">abhinavleo</a><a href="https://dmi.pravinmishra.com/s/YOUR-GITHUB-USERNAME.html"><em>.html</em></a><em> · Start your DevOps journey: </em><a href="https://dmi.pravinmishra.com/?utm_source=student&amp;utm_medium=ps-blog&amp;utm_campaign=cohort3"><em>https://dmi.pravinmishra.com/?utm_source=student&amp;utm_medium=ps-blog&amp;utm_campaign=cohort3</em></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf9b4b13d2c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The future 2.0]]></title>
            <link>https://medium.com/@abhinav1712003/the-future-2-0-152477599749?source=rss-ae6091faa7b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/152477599749</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[new-journey]]></category>
            <dc:creator><![CDATA[Abhinav]]></dc:creator>
            <pubDate>Wed, 01 Jul 2026 06:29:43 GMT</pubDate>
            <atom:updated>2026-07-01T06:29:43.682Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jtSDZCrJQElKsagMXCqtag.jpeg" /></figure><p><strong>This post is a part of DevOps Micro Internship with Agentic AI Cohort-3 by </strong><a href="https://www.linkedin.com/in/pravin-mishra-aws-trainer/"><strong>Pravin Mishra</strong></a><strong>. You can start your DevOps journey by joining this </strong><a href="https://discord.pravinmishra.com/"><strong>Discord community</strong></a><strong> ( </strong><a href="https://discord.pravinmishra.com/"><strong>https://discord.pravinmishra.com/</strong></a><strong> ).</strong></p><p>Every journey starts with a beginning , and mine started with curiosity about how technology works. My journey from a beginner exploring Linux and cloud technologies turned into a strong DevOps engineering career. I built my foundation by learning new concepts, experimenting consistently, and creating real-world projects. Instead of just watching tutorials, I spent time practicing what I learned and understanding how things worked behind the scenes. I progressed from learning the basics to working as a DevOps Engineer who contributed to real world systems. I worked with cloud platforms, automation tools, and modern DevOps practices. I built projects that proved my skills and created a portfolio that showed my journey and growth. Every project taught me something new, whether it was fixing deployment issues, writing automation scripts, or setting up cloud infrastructure.</p><p>I was no longer the same person who only followed tutorials. I became an engineer who understood why systems worked the way they did and how they could be improved. Instead of looking for answers, I learned how to troubleshoot problems, find the root cause of issues, and build better solutions through practice.</p><p>My GitHub portfolio reflected my practical experience through projects involving cloud automation, scripting, deployments, and infrastructure. I kept improving my skills by documenting what I learned, writing blogs, trying new technologies, and earning AWS and Azure certifications. Looking back at my portfolio, it clearly showed how much I had improved over the years. With three to four years of experience, I contributed to system design decisions and helped teams deliver software faster and more reliably. I worked closely with developers, shared my knowledge with team members, and helped beginners who were starting their DevOps journey. I believed that learning was even more valuable when it was shared with others.</p><p>The biggest change? I became more disciplined, curious, and focused on solving real problems. The person who once doubted whether he belonged in technology had grown into a confident DevOps Engineer who enjoyed learning, building, and continuously improving every day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=152477599749" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>