У нас вы можете посмотреть бесплатно Connect with Community или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Today’s Connect with Community call centered on one powerful story that reminded us exactly why NextWork exists: turning real-world problems into learnable, buildable tech skills that make a difference. The Story That Stuck with Us sify111 a public health professional from the U.S. South, brought a story that hit home. During the COVID era, many rural health clinics were still working with paper forms. Outbreak data moved around on flash drives, and underfunded infrastructure made real-time tracking nearly impossible. sify111 described what it was like standing in the middle of that, watching data delay impact care and realizing something deeper: There was no shared language between the people who understood the health crisis and the people who could build the solutions. That gap, between domain experts and technologists, is exactly the bridge NextWork exists to build. Why This Resonates with Our Community Sifi’s story captures so much about what makes our community unique: Non-traditional backgrounds are a strength. Sifi didn’t come from “tech.” They came from public health and that real-world perspective is what gives meaning to the tools and technologies we teach. Tech skills matter most when they meet real problems. Understanding Cloud, DevOps, AI, data pipelines is the difference between paper charts in a rural clinic and real-time data that saves lives. Our learners are already building the bridge. On the same call, Roy P shared new ideas for hands-on project series around Infrastructure as Code, Terraform, and CI/CD. ShySinister and Sean suggested a “tool setup” journey to make sure no beginner gets stuck on config steps. Others talked about experimenting with AI-powered DevOps workflows - especially when there's a concern of AI replacing DevOps roles. HairyBrewer emphasized that DevOps is fundamentally the intersection of development and operations. Development and operations may change, but the need for that intersection is a constant. AI will change how we implement DevOps, not whether DevOps is needed. We even had a question from YouTube on how to work start a new role in the US when English isn't your first language. To that, Hairybrewer addressed it beautifully: join the Connect with Community calls with NextWork. Practice your English AND your technical communication - both are skills that can be learned! Join our community on Discord: / discord