From Intern to DevOps Engineer: Lessons Learned in My First Two Years
summary
Computer Science coursework does not prepare for operating a shared tenant multi-cluster at The New York Times on AWS and trying to specialize in Kubernetes too early proves counterproductive. The path described is concrete: define task scope, build a small foundation, attempt the task, get stuck, then ask for help. Built outcomes include filling missing documentation, posting short demos, and creating a 24 7 workspace for impromptu collaboration. Promotion expectations miss the reality that new gaps appear as responsibilities grow.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:34At the new grad
- 0:50Cloud Runtime Team
- 1:05The Gap
- 1:20Bad Practices
- 1:35Missing a Promotion
- 1:50Feedback
- 2:20Look for help
- 2:35Understand the bigger picture
- 2:50Take on difficult tasks
- 3:05Learn for the job not the job
- 3:36Ask for help
- 3:51Nontechnical opportunities
- 4:21Tips for remote work
- 4:36Celebrate your accomplishments
- 4:50Gap cant be bridged
- 5:05Outro
related talks
39mMaking Infrastructure More Friendly for Beginners
06mIgnites - Zero to DevOps in less than a year...
06mIgnite: Moving from regular sysadmin to DevOps
45mGrowing into new roles beyond the cloud
22mFrom free-kicks to git commits
06mDevOpsDays Boston 2023 Lightning Talks: Jason Li
36mDevOps in Outsource… Really!
30mMy Cloud Native journey