👨‍💻 3 minutes on whether AI will eat DevOps jobs

👨‍💻 3 minutes on whether AI will eat DevOps jobs

TechWorld with Nana 81 078 просмотров 2 696 лайков

Machine-readable: Markdown · JSON API · Site index

Поделиться Telegram VK Бот
Транскрипт Скачать .md
Анализ с AI
Описание видео
Watched a senior engineer waste 3 hours fixing a Terraform mess yesterday that ChatGPT fixed in like 40 seconds. Kinda crazy to be honest. However here's what I also saw since I started using AI for engineering work: It's not really about who can write the configs faster or by heart - it's more about whether you what even needs configuring in the first place. Like understanding your checkout system needs different capacity during holiday sales vs random Tuesday mornings. The DevOps engineers who are crushing it aren't just good script writers any more - they are the ones who understand what the business actually needs and then make the tech do that. Quick video with more thoughts ☝️ Got those free calls this week if ur interested in specific feedback: https://bit.ly/3Xew2eN

Оглавление (1 сегментов)

Segment 1 (00:00 - 03:00)

Everyone is asking, "Will AI take my DevOps job? " But here is something that people don't talk about. AI is already automating repetitive tasks. Think of Terraform configuration files or writing basic pipelines, troubleshooting hundreds or thousands of lines of logs. But here is what AI cannot do. Understand your business context. When your production crashes at 3:00 a. m., AI cannot decide whether to roll back or push forward based on your company's risk tolerance, for example. It cannot architect a system that balances cost, performance, and team capabilities and team resources. It also cannot negotiate with security teams or explain the tradeoffs to executives. And DevOps is fundamentally about decision making under uncertainty about various parts of your system. And AI is a tool that makes good DevOps engineers faster and more efficient in their work. And I know that most of you have heard this, but I want to highlight it here. The engineers who will struggle or be most under risk because of AI are going to be ones doing purely mechanical work. And you will know immediately if you are one of them. If you are stuck doing the same type of manual repetitive mechanical work that is the easiest part to automate through AI. But the engineers who will thrive because of AI. So actually be more at an advantage because of AI than without it are going to be ones who use AI to handle the grunt work that is simple to automate but also takes a lot of time while they themselves focus on architecture and strategy. Now, if this resonates and if you're really serious about building an AI proof engineering career, specifically with DevOps skills, me and my team are actually doing free orientation calls where my team will help you identify exactly what skills will matter in 2026 and beyond. Dig deeper in your individual situation and give you a clear road map. No strings attached, just pure value for you to help you find a direction and clarity about what you need to do next. You're going to find the link in the bio or in the comments, but know that these calls fill up pretty fast because we genuinely help people make informed decisions with more clarity. So, be sure to reserve your spot fast and take advantage of this because we only going to be doing this for a few months for

Другие видео автора — TechWorld with Nana

Ctrl+V

Экстракт Знаний в Telegram

Экстракты и дистилляты из лучших YouTube-каналов — сразу после публикации.

Подписаться

Дайджест Экстрактов

Лучшие методички за неделю — каждый понедельник