<?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[The DevOps Mindset - Medium]]></title>
        <description><![CDATA[DevOps is more than tools — it’s a mindset. Learn how teams excel together, value continuous improvement, share responsibility, and stay open to change. Dive into the core ideas behind DevOps, made simple for everyone, regardless of language. - Medium]]></description>
        <link>https://medium.com/devops-mindset?source=rss----c19fe2342b26---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The DevOps Mindset - Medium</title>
            <link>https://medium.com/devops-mindset?source=rss----c19fe2342b26---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:25:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/devops-mindset" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AI Is Not Replacing DevOps Fundamentals. It’s Making Them More Important.]]></title>
            <link>https://medium.com/devops-mindset/ai-is-not-replacing-devops-fundamentals-its-making-them-more-important-74a48a871630?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/74a48a871630</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Sun, 16 Aug 2026 14:43:15 GMT</pubDate>
            <atom:updated>2026-08-16T14:43:16.310Z</atom:updated>
            <content:encoded><![CDATA[<p>This week, I received an email from one of my subscribers.</p><p>He wrote:</p><p>“I’m in the early stages of learning DevOps. AI is changing everything so fast that I’m afraid I’ll become irrelevant. Should I focus on building fundamentals first, or should I use AI for every problem I don’t know how to solve?”</p><p>I think many beginners are asking themselves the same question. My answer is simple.</p><p><strong>Do both, but in the right order.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iM-nfa1azqY0NUie4QgnAg.jpeg" /></figure><p>When I started learning DevOps, AI assistants didn’t exist.</p><p>If I wanted to understand why a Linux command failed, I had to search through blog posts, Stack Overflow, documentation, DevOps forums, and YouTube videos.</p><p>Sometimes it took hours just to understand one error.</p><p>Today, AI can often explain the problem in seconds, and that’s an incredible advantage.</p><p>But here is what worries me about AI: Some people are replacing learning with prompting.</p><p><strong>Instead of asking:</strong></p><p>“Why does this work?”</p><p><strong>They ask:</strong></p><p>“Generate the solution.”</p><p>Those are very different approaches.</p><p>Imagine you are learning Linux.</p><p>You ask AI:</p><p><em>“Write a Bash script that deletes files older than 30 days.”</em></p><p>AI gives you a perfect script that works. Great.</p><p>Now someone asks you in an interview:</p><p><em>“Can you explain what find, -mtime, -exec, and xargs are doing?”</em></p><p>If your answer is “I’m<em> not sure. AI wrote it,” y</em>ou have learned almost nothing.</p><p>AI is an amazing teacher, and it’s a terrible replacement for understanding.</p><p>The engineers who will succeed over the next few years won’t be the ones who never use AI but the ones who know enough to recognize when AI is wrong.</p><p>And yes, it <strong>will</strong> be wrong.</p><p>I’ve seen AI confidently recommend commands that would fail in production, misunderstand Kubernetes configurations, or invent configuration options that don’t even exist.</p><p>Without fundamentals, you can’t tell the difference.</p><p>Here is the approach I would recommend if you are just starting your DevOps journey:</p><ul><li>Learn the fundamentals first: Linux, networking, Git, scripting, cloud basics, and how software gets from a developer’s laptop into production.</li><li>Use AI as your tutorial, not your substitute.</li><li>Every time AI gives you an answer, ask one more question: <strong>“Why?”</strong></li><li>Try the solution yourself. Break it. Fix it. Experiment until you understand it.</li></ul><p>Remember, companies don’t hire junior DevOps engineers because they already know everything.</p><p>They hire people who can learn, solve problems, and keep improving.</p><p>AI makes learning faster.</p><p>It doesn’t eliminate the need to learn.</p><p>In fact, I think fundamentals have become even more valuable.</p><p>Because when everyone has access to the same AI tools, the real difference is not who can write the best prompt.</p><p><strong>It’s who can tell whether the answer makes sense.</strong></p><p>Every Saturday, I share practical tutorials, tips, and real-world insights designed for junior DevOps engineers and anyone aspiring to break into the DevOps world.</p><p>Join the journey and level up your DevOps skills one email at a time.</p><p>Subscribe here: <a href="https://junior-devops-hub.ck.page/">https://junior-devops-hub.ck.page</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74a48a871630" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-mindset/ai-is-not-replacing-devops-fundamentals-its-making-them-more-important-74a48a871630">AI Is Not Replacing DevOps Fundamentals. It’s Making Them More Important.</a> was originally published in <a href="https://medium.com/devops-mindset">The DevOps Mindset</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Agents Are Coming Faster Than You Think]]></title>
            <link>https://medium.com/devops-mindset/ai-agents-are-coming-faster-than-you-think-5bd4064993c6?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/5bd4064993c6</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 09:10:24 GMT</pubDate>
            <atom:updated>2026-08-04T09:10:24.506Z</atom:updated>
            <content:encoded><![CDATA[<p>Every week, dozens of DevOps announcements flood LinkedIn, Reddit, and tech news sites.</p><p>Most of them sound impressive.</p><p>Few of them actually change how we’ll work.</p><p>This week felt different.</p><p>When I looked through the announcements, I noticed a pattern.</p><p>Almost every major vendor is trying to automate another piece of the software delivery lifecycle. Not just with scripts or workflows, but with AI agents that can make decisions and perform work on behalf of engineers.</p><p>We’re moving from “automation” to “delegation.”</p><p>Here are the stories that stood out and why I think they matter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iM-nfa1azqY0NUie4QgnAg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@coopery?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mohamed Nohassi</a> on <a href="https://unsplash.com/photos/a-white-robot-with-blue-eyes-and-a-laptop--0xMiYQmk8g?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>1. Kubernetes upgrades just became less risky.</h3><p>One of the most practical announcements this week came from AWS.</p><p>Amazon EKS now allows you to roll back a Kubernetes version upgrade within seven days.</p><p>If you’ve ever managed production Kubernetes clusters, you know why this feature is important.</p><p>Even after testing, problems sometimes only appear after real production traffic hits the cluster.</p><p>Before this update, upgrading often felt like crossing a bridge that disappeared behind you.</p><p>Now there is a safety net.</p><p>Will this replace proper testing?</p><p>Of course not.</p><p>But reducing operational risk is always a good thing.</p><h3>2. GitHub wants Dependabot to be less annoying.</h3><p>Most teams agree that dependency updates are important.</p><p>Most teams also agree that opening dozens of pull requests every week is not.</p><p>GitHub introduced a default cooldown policy for Dependabot updates.</p><p>Instead of constantly generating update PRs, teams can better control when updates arrive.</p><p>It’s a small feature.</p><p>But it’s solving a real problem.</p><p>Good DevOps is not about automating everything.</p><p>It’s about automating without creating more noise.</p><h3>3. AI agents are becoming part of the delivery pipeline.</h3><p>This week’s biggest trend wasn’t Kubernetes or the cloud.</p><p>It was AI agents.</p><p>Harness introduced Autonomous Worker Agents that can handle work between writing code and deploying software.</p><p>IBM expanded Bob with multi-agent workflows.</p><p>AWS launched the GuardDuty Investigation Agent to automate security investigations.</p><p>Notice the pattern?</p><p>These companies are not trying to replace engineers.</p><p>They are trying to eliminate repetitive work.</p><p>The interesting question is not whether AI will become part of DevOps.</p><p>It already is.</p><p>The real question is:</p><p>Which parts of your daily work should remain human decisions, and which should be delegated?</p><h3>4. Observability is getting smarter.</h3><p>Grafana Assistant now supports more than 30 data sources.</p><p>Instead of searching across dashboards, logs, and metrics manually, engineers can ask questions using natural language.</p><p>Observability tools have traditionally been great at collecting data.</p><p>Finding the answer inside that data has always been the harder part.</p><p>This is where AI could genuinely save time during incidents.</p><h3>5. Security is becoming more automated.</h3><p>Security wasn’t left behind this week.</p><p>IBM, Red Hat, and Deloitte announced a collaboration focused on protecting the software supply chain against increasingly automated attacks.</p><p>At the same time, AWS introduced AI-assisted threat investigations.</p><p>Attackers are using more automation.</p><p>Defenders are responding the same way.</p><p>For DevOps engineers, security is no longer something handled only by another department.</p><p>It’s becoming another responsibility built directly into the platform.</p><h3>6. Infrastructure efficiency still matters.</h3><p>AI dominated the headlines, but one story reminded me that fundamentals haven’t changed.</p><p>Uber shared details about its “Zero Growth Stack,” an engineering strategy focused on scaling infrastructure while keeping infrastructure and AI costs under control.</p><p>That’s an important reminder.</p><p>New technology is exciting.</p><p>Keeping cloud bills under control is still part of the job.</p><p>Platform engineering is not just about making developers faster.</p><p>It’s also about making infrastructure sustainable.</p><h3>My biggest takeaway</h3><p>If I had to summarize this week in one sentence, it would be this:</p><p><strong>DevOps tools are evolving from helping engineers do work to helping engineers decide what work needs to be done.</strong></p><p>That’s a subtle but important shift.</p><p>Five years ago we automated deployments.</p><p>Today we are starting to automate investigations, dependency management, security analysis, and operational decisions.</p><p>Will AI replace DevOps engineers?</p><p>I don’t think so.</p><p>But I do think it will replace many repetitive tasks that engineers never enjoyed doing in the first place.</p><p>The engineers who thrive won’t necessarily be the ones who know every new AI tool.</p><p>They’ll be the ones who understand systems well enough to decide when automation should be trusted and when it shouldn’t.</p><p>That’s still a very human skill.</p><p>I’m a DevOps expert with 15 years in IT.</p><p>Every Saturday, I share hands-on tips for junior DevOps engineers and those breaking into the field.</p><p>🎁 Get a free “Is a DevOps Career Right for You?” — A 38-page Beginner’s Guide to help you decide if DevOps is your next big move.</p><p>Subscribe: <a href="https://junior-devops-hub.ck.page/">https://junior-devops-hub.ck.page</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bd4064993c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-mindset/ai-agents-are-coming-faster-than-you-think-5bd4064993c6">AI Agents Are Coming Faster Than You Think</a> was originally published in <a href="https://medium.com/devops-mindset">The DevOps Mindset</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps is not about tools (I learned the hard way)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/devops-mindset/devops-is-not-about-tools-i-learned-the-hard-way-3ef2f8f800fb?source=rss----c19fe2342b26---4"><img src="https://cdn-images-1.medium.com/max/2600/1*7OnOS2Hlt5vIKFVozBhN-g.jpeg" width="5184"></a></p><p class="medium-feed-snippet">When I joined my first DevOps job, I felt like I had landed in a foreign country.</p><p class="medium-feed-link"><a href="https://medium.com/devops-mindset/devops-is-not-about-tools-i-learned-the-hard-way-3ef2f8f800fb?source=rss----c19fe2342b26---4">Continue reading on The DevOps Mindset »</a></p></div>]]></description>
            <link>https://medium.com/devops-mindset/devops-is-not-about-tools-i-learned-the-hard-way-3ef2f8f800fb?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/3ef2f8f800fb</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops-mindset]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Sun, 28 Sep 2025 07:57:41 GMT</pubDate>
            <atom:updated>2025-09-28T07:57:16.050Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Danger of Over-Engineering in DevOps]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/devops-mindset/the-danger-of-over-engineering-in-devops-62b65bf1db56?source=rss----c19fe2342b26---4"><img src="https://cdn-images-1.medium.com/max/2600/1*OcoQk7n0SpGPK3wdwctcGA.jpeg" width="4608"></a></p><p class="medium-feed-snippet">One of the most common mistakes I see from junior DevOps engineers is over-engineering simple problems.</p><p class="medium-feed-link"><a href="https://medium.com/devops-mindset/the-danger-of-over-engineering-in-devops-62b65bf1db56?source=rss----c19fe2342b26---4">Continue reading on The DevOps Mindset »</a></p></div>]]></description>
            <link>https://medium.com/devops-mindset/the-danger-of-over-engineering-in-devops-62b65bf1db56?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/62b65bf1db56</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Sat, 27 Sep 2025 14:27:33 GMT</pubDate>
            <atom:updated>2025-09-27T14:27:04.934Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Two Mindset Shifts That Changed Everything for Me in DevOps]]></title>
            <link>https://medium.com/devops-mindset/two-mindset-shifts-that-changed-everything-for-me-in-devops-3c5635126a66?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/3c5635126a66</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Wed, 13 Aug 2025 16:07:42 GMT</pubDate>
            <atom:updated>2025-08-05T13:48:06.074Z</atom:updated>
            <content:encoded><![CDATA[<p>When I started learning DevOps, I did what most beginners do.</p><p>I chased tools.</p><p>Docker. Kubernetes. AWS. Terraform.</p><p>I followed tutorials, built pet projects, and even passed a few certifications. I could technically use the tools, but I didn’t really understand <strong>why</strong> I was using them. I didn’t know what real problems they were solving.</p><p>At some point, I hit a wall.</p><p>And then everything changed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7OnOS2Hlt5vIKFVozBhN-g.jpeg" /></figure><h3>Shift 1: From Tool-Oriented to Solution-Oriented</h3><p>One day I stopped asking.<br><strong>“What should I learn next?”</strong><br>And I started asking,<br><strong>“What problem am I solving?”</strong></p><p>Instead of trying to master every hot new tool, I imagined I was building the infrastructure for a real company. My own startup.</p><p>And that’s when things clicked.</p><p>I didn’t start with tools anymore. I started with <strong>needs</strong>, then found the right solution.</p><p>Like this:</p><ul><li>I need virtual servers → <strong>Use EC2 or VMware.</strong></li><li>I need version control → <strong>Use Git.</strong></li><li>I need to containerize microservices → <strong>Use Docker &amp; Docker Compose.</strong></li><li>I need to orchestrate them → <strong>Use Kubernetes.</strong></li><li>I need centralized logs → <strong>Use the ELK stack.</strong></li><li>I need to monitor my servers → <strong>Use Grafana.</strong></li></ul><p>Every tool I used became the result of <strong>thinking</strong>, not the starting point.</p><p>That mindset made my learning 10x faster and more meaningful.<br>I wasn’t just practicing commands. I was solving real infrastructure challenges.</p><h3>Shift 2: From Tech Thinking to Business Thinking</h3><p>This one took me longer to realize.</p><p>Even after I became confident with tools and architecture, I still missed something critical: <strong>the business context</strong>.</p><p>I used to think,</p><p>“This is the best practice. Why don’t they use it?”</p><p>But now I understand that the <strong>best</strong> technical solution isn’t always the <strong>right</strong> one for the business.</p><ul><li>Maybe it’s too expensive.</li><li>Maybe it’s too complex for the team.</li><li>Maybe it solves a problem no one really has.</li><li>Maybe it’s creating another problem.</li></ul><p>As DevOps engineers, we are not just building systems.<br>We are solving business problems with technology.</p><p>That second mindset shift changed how I work, how I think, and how I communicate with teams.</p><h3>If you are new to DevOps, remember this:</h3><p>✅ Tools matter.<br>✅ Tutorials help.<br>✅ Projects build experience.</p><p>But the <strong>right mindset</strong> will take you further than any certification or Udemy course.</p><p>Think in terms of <strong>solutions</strong>, not tools.<br>Think in terms of <strong>business value</strong>, not just technical elegance.</p><p>That’s what makes you a real DevOps engineer.</p><p>I’m a DevOps expert with 15 years in IT.</p><p>Every Saturday, I share hands-on tips for junior DevOps engineers and those breaking into the field.</p><p>🎁 Get a free “Is a DevOps Career Right for You?” — A 38-page Beginner’s Guide to help you decide if DevOps is your next big move.</p><p>Subscribe: <a href="https://junior-devops-hub.ck.page/">https://junior-devops-hub.ck.page</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c5635126a66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-mindset/two-mindset-shifts-that-changed-everything-for-me-in-devops-3c5635126a66">Two Mindset Shifts That Changed Everything for Me in DevOps</a> was originally published in <a href="https://medium.com/devops-mindset">The DevOps Mindset</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Senior DevOps Engineer Asked Me for Advice. Here’s What I Told Him.]]></title>
            <link>https://medium.com/devops-mindset/a-senior-devops-engineer-asked-me-for-advice-heres-what-i-told-him-7992b60ecd2e?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/7992b60ecd2e</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Wed, 13 Aug 2025 16:07:26 GMT</pubDate>
            <atom:updated>2025-09-24T13:15:01.574Z</atom:updated>
            <content:encoded><![CDATA[<p>A senior DevOps engineer reached out to me:</p><p>“Andrey, I’m suffering a lot to level up as a senior engineer and in interviews. I always found your guidelines exceptionally useful. If you can guide me, I’ll be highly grateful.”</p><p>Here is what I told him and what I tell any junior or mid-level DevOps engineer feeling stuck.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3j1gmbJpqJHowtBYhlrBUw.jpeg" /></figure><p>Being a senior is not just about technical skills. It’s about how you think, communicate, and lead.</p><p>If you want to be seen and trusted as a senior, start doing these 6 things:</p><h4>1️⃣ Own outcomes, not just tasks.</h4><p>Do not say “this pipeline works.” Say, “It’s integrated, tested, documented, monitored, and it solves a real problem.”</p><p>Be proactive.</p><p>Do not just close your ticket, but always search for ways to improve your environment. Search for the ways to save the team members time and the company’s money.</p><p>Think business needs, not tasks.</p><h4>2️⃣ Communicate like a leader.</h4><p>Document what you do. Share decisions. Write internal guides. Search for why, not just what.</p><p>Aim to see the big picture.</p><p>Think about the business value of every decision you make. Business comes first.</p><h4>3️⃣ Lead without the title.</h4><p>Mentor juniors. Review PRs with empathy. Help the team grow with or without authority.</p><p>If you see that some team members are weak in some topic, prepare and present about it.</p><p>Teach them without anyone ask.</p><p>Be proactive.</p><h4>4️⃣ Think business-first.</h4><p>Ask why the task matters. What is the user pain? What does success look like?</p><p>As a DevOps professional, your real mission is to support the business, not your favorite stack.</p><h4>5️⃣ Stop waiting to be promoted.</h4><p>Act like a senior now. Step up. Volunteer. Suggest improvements. Take initiative before anyone asks.</p><p>You will be promoted only if you show your potential. You should demonstrate leadership qualities even prior to receiving the promotion.</p><h4>6️⃣ Tell stories in interviews.</h4><p>Not “I used Terraform.” But: “We had this issue. I proposed X. Here is what happened. Here is what I learned.”</p><p>Talk in <a href="https://medium.com/devops-mindset/how-to-answer-questions-in-a-devops-interview-using-the-star-format-situation-task-action-b8ec0be231e1">STAR format</a> on the interviews.</p><p>📌 You don’t get promoted and then start acting like a senior.</p><p>You act like a senior, and then they have no choice but to promote you.</p><p>I’m a DevOps expert with 15 years in IT.</p><p>Every Saturday, I share hands-on tips for junior DevOps engineers and those breaking into the field.</p><p>🎁 Get a free “Is a DevOps Career Right for You?” — A 38-page Beginner’s Guide to help you decide if DevOps is your next big move.</p><p>Subscribe: <a href="https://junior-devops-hub.ck.page/">https://junior-devops-hub.ck.page</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7992b60ecd2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/devops-mindset/a-senior-devops-engineer-asked-me-for-advice-heres-what-i-told-him-7992b60ecd2e">A Senior DevOps Engineer Asked Me for Advice. Here’s What I Told Him.</a> was originally published in <a href="https://medium.com/devops-mindset">The DevOps Mindset</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Real Reason why you cannot pass junior DevOps interview (Not technical knowledge)]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/devops-mindset/real-reason-why-you-cannot-pass-junior-devops-interview-not-technical-knowledge-71681b18bbbe?source=rss----c19fe2342b26---4"><img src="https://cdn-images-1.medium.com/max/1920/1*ryqY0wFIA7XgcuKGdOiShw.jpeg" width="1920"></a></p><p class="medium-feed-snippet">The technical interview is a difficult and stressful part of the hiring process.</p><p class="medium-feed-link"><a href="https://medium.com/devops-mindset/real-reason-why-you-cannot-pass-junior-devops-interview-not-technical-knowledge-71681b18bbbe?source=rss----c19fe2342b26---4">Continue reading on The DevOps Mindset »</a></p></div>]]></description>
            <link>https://medium.com/devops-mindset/real-reason-why-you-cannot-pass-junior-devops-interview-not-technical-knowledge-71681b18bbbe?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/71681b18bbbe</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 14:35:02 GMT</pubDate>
            <atom:updated>2025-03-10T16:42:27.278Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[6 Challenges Every Junior DevOps Engineer Faces and How to Overcome Them]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/devops-mindset/6-challenges-every-junior-devops-engineer-faces-and-how-to-overcome-them-f76c86221691?source=rss----c19fe2342b26---4"><img src="https://cdn-images-1.medium.com/max/1904/1*IoY1XN-uqRfyVafiMrM7rw.jpeg" width="1904"></a></p><p class="medium-feed-snippet">In this article, I will talk about six challenges every junior DevOps engineer faces and how to overcome them.</p><p class="medium-feed-link"><a href="https://medium.com/devops-mindset/6-challenges-every-junior-devops-engineer-faces-and-how-to-overcome-them-f76c86221691?source=rss----c19fe2342b26---4">Continue reading on The DevOps Mindset »</a></p></div>]]></description>
            <link>https://medium.com/devops-mindset/6-challenges-every-junior-devops-engineer-faces-and-how-to-overcome-them-f76c86221691?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/f76c86221691</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[junior-devops]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 14:33:56 GMT</pubDate>
            <atom:updated>2025-08-17T07:07:48.508Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to pass the technical Junior DevOps interview. Tip from a real-life experience.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/devops-mindset/how-to-pass-the-junior-devops-interview-tip-from-a-real-life-experience-4ee2c26c22f5?source=rss----c19fe2342b26---4"><img src="https://cdn-images-1.medium.com/max/1920/1*Vvf_9YS91LvMmko-QJyQCw.jpeg" width="1920"></a></p><p class="medium-feed-snippet">The technical interview is probably the most difficult and stressful part of the hiring process.</p><p class="medium-feed-link"><a href="https://medium.com/devops-mindset/how-to-pass-the-junior-devops-interview-tip-from-a-real-life-experience-4ee2c26c22f5?source=rss----c19fe2342b26---4">Continue reading on The DevOps Mindset »</a></p></div>]]></description>
            <link>https://medium.com/devops-mindset/how-to-pass-the-junior-devops-interview-tip-from-a-real-life-experience-4ee2c26c22f5?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/4ee2c26c22f5</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[technical-interview]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 14:33:26 GMT</pubDate>
            <atom:updated>2024-08-21T17:17:06.528Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to land your first DevOps job. Practical advice based on my own experience.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/devops-mindset/how-to-land-your-first-devops-job-practical-advice-based-on-my-own-experience-45372afc1c2c?source=rss----c19fe2342b26---4"><img src="https://cdn-images-1.medium.com/max/2600/1*EADm3S23kE-tpRV2T5IQ6w.jpeg" width="6000"></a></p><p class="medium-feed-snippet">In this article, I&#x2019;ll provide you with practical advice on how to improve your chances to make HR notice your resume and LinkedIn account.</p><p class="medium-feed-link"><a href="https://medium.com/devops-mindset/how-to-land-your-first-devops-job-practical-advice-based-on-my-own-experience-45372afc1c2c?source=rss----c19fe2342b26---4">Continue reading on The DevOps Mindset »</a></p></div>]]></description>
            <link>https://medium.com/devops-mindset/how-to-land-your-first-devops-job-practical-advice-based-on-my-own-experience-45372afc1c2c?source=rss----c19fe2342b26---4</link>
            <guid isPermaLink="false">https://medium.com/p/45372afc1c2c</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Andrey Byhalenko]]></dc:creator>
            <pubDate>Mon, 11 Nov 2024 14:31:33 GMT</pubDate>
            <atom:updated>2025-08-17T07:18:57.486Z</atom:updated>
        </item>
    </channel>
</rss>