will my dad LOSE his job? (a TRADITIONAL IT infrastructure engineer)

About this video

NetworkChuck asks whether his dad — Chuck Keith, introduced as an infrastructure manager at Supreme Lending focused on systems and storage — will lose his traditional infrastructure job as IT shifts to the cloud. The dad describes traditional work as on-prem storage, virtualization with VMware and Hyper-V, Active Directory, building servers and break-fix troubleshooting. Chuck says those skills remain valuable, but companies are moving some workloads to public cloud for reasons he frames as three laws: economics (avoiding expensive server refreshes, with a trade-off to weigh), physics (latency), and the law of the land (security and compliance that may require owned data centers). He adds cloud-native architecture — microservices, containers and Kubernetes — plus automation tools such as Ansible, Puppet and Chef, which together move the role toward DevOps. The dad confirms his company is becoming hybrid, putting some domain controllers and development in Azure, with microservices only a future goal. Chuck argues adoption is gradual, project-by-project rather than overnight, and presents a second path besides hiring DevOps staff or retraining for public cloud: extending on-prem with VMware vSphere with Tanzu via sponsor Dell Technologies APEX, so familiar tools like vCenter can manage both VMs and Kubernetes on-prem and across clouds. His conclusion, echoed by his dad, is no — the role is not disappearing, on-prem is not going away, but traditional engineers must keep adapting, including some programming such as PowerShell or Python and cloud study.

Key takeaways

• Traditional infrastructure skills — storage, virtualization, Active Directory, server management and troubleshooting — are described as still valuable and in demand
• Cloud migration decisions are framed by economics, latency/physics, and security/compliance constraints, leading most shops toward hybrid rather than all-cloud
• The new skill stack to add is cloud-native technology (containers, Kubernetes, microservices), automation (Ansible, Puppet, Chef) and some programming
• Adoption in the dad’s company is gradual and project-led — some Azure workloads now, microservices later — not an overnight switch that fires on-prem staff
• An alternative path is running cloud-native workloads on-prem with familiar virtualization tooling, but continuous learning is still required to stay relevant

Episode details: published June 3, 2021 · 15:30 long. Summary written by Self Growth Videos from the episode itself. Business results and any income figures mentioned are NetworkChuck’s own claims, shared for education — they are not typical or guaranteed.

← Previous: fiber optic cables (what you NEED to know) // FREE CCNA // EP 13 · Next: apt, dpkg, git, Python PiP (Linux Package Management) // Linux for Hackers // EP 5 →

All NetworkChuck videos · NetworkChuck profile · NetworkChuck on YouTube