<?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 Kishore Kumar  on Medium]]></title>
        <description><![CDATA[Stories by Kishore Kumar  on Medium]]></description>
        <link>https://medium.com/@kishorekumar_6753?source=rss-4f8e900c5828------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LOqkOon8oPLO9SLwbvCOBA.png</url>
            <title>Stories by Kishore Kumar  on Medium</title>
            <link>https://medium.com/@kishorekumar_6753?source=rss-4f8e900c5828------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:07:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kishorekumar_6753/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[CRASH & LEARN #1 — The Day I Hit Enter and Instantly Regretted Everything]]></title>
            <link>https://medium.com/@kishorekumar_6753/crash-learn-1-the-day-i-hit-enter-and-instantly-regretted-everything-3ee6aabcc0cc?source=rss-4f8e900c5828------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ee6aabcc0cc</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[baremetal]]></category>
            <category><![CDATA[iptables]]></category>
            <dc:creator><![CDATA[Kishore Kumar ]]></dc:creator>
            <pubDate>Sun, 23 Nov 2025 11:34:35 GMT</pubDate>
            <atom:updated>2025-11-23T11:55:21.465Z</atom:updated>
            <content:encoded><![CDATA[<h3>CRASH &amp; LEARN #1 — The Day I Hit Enter and Instantly Regretted Everything</h3><p>I’m starting a new series called “<strong>Crash &amp; Learn</strong>,” where I share real mistakes I’ve made so others can learn from them. Here’s the <strong>first story</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6wqY3HDmxrbg-cU_VdlHg.png" /></figure><p>It started on what felt like a normal, productive day. I was working on our <strong>office development bare-metal server</strong>, connected through SSH from my local machine. My goal was to set up traffic routing using <strong>iptables</strong>. After hours of trying different configurations, reading documentation, and even asking ChatGPT for help, nothing seemed to work.</p><p>Eventually, frustration took over. Tired and irritated, I made a mistake every DevOps engineer dreads — I ran a command I didn’t fully understand. Worse, it was a command I had copied directly from ChatGPT without thinking twice:</p><pre>sudo iptables -F</pre><p>Immediately, my SSH session closed. Everything went silent. I had just wiped all firewall rules, including the one that allowed me to connect remotely. In an instant, I locked myself out of the server. No SSH. No access. No way back in.</p><p>For a few tense minutes, it felt like a total disaster. Anyone who manages important servers knows the sinking feeling when a single careless command brings everything to a halt.</p><p>Fortunately, we had a fallback: <strong>IPMI access</strong>. Through the remote management interface, I was able to regain control and undo the damage. The relief was enormous — and so was the lesson.</p><h3>What I Learned</h3><p>This mistake taught me a simple but important rule:</p><p><strong>Don’t trust any command blindly — whether it’s from ChatGPT, a forum, or even a colleague. Stop and think before you hit Enter. It’s a basic rule, but one we often forget until it’s too late.</strong></p><p>When a command touches networking, firewall rules, or core system settings, it deserves extra caution, a double-check, and a backup plan. One careless moment — one line you didn’t fully think through — can lock you out, take systems down, and cost you hours of recovery.</p><p>This time I was lucky. I had IPMI access.<br> Next time, I might not be.</p><p>And that’s exactly why I’m sharing these stories: <strong>so my crashes can become someone else’s lessons.</strong></p><p>⭐ <strong>Enjoying these Crash &amp; Learn stories?</strong></p><blockquote><strong>P.S.</strong> You can learn the concepts from docs, but real-world mistakes are rare to see.<br>If this story helped you, feel free to support the series.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ee6aabcc0cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>