Hey everyone, I'm a DevOps engineer with a few years of experience mainly in areas like CI/CD, Kubernetes, and cloud tools. While I'm really solid with AWS and Terraform, I've started to notice that my foundational knowledge is lacking. For instance, I can manage Kubernetes deployments but wouldn't be able to clearly describe a `kubelet`. I know my way around Linux and networking tools, but I often feel insecure explaining the underlying concepts like NAT or TCP. I've never developed a proper application, only written scripts and YAML files, and I'm interested in learning Go but need help figuring out how to approach that. I want to fill these knowledge gaps, especially as I prepare for future interviews, but I don't want to overwhelm myself. Long study sessions just don't work for me as I lose focus quickly. Any advice on how I can bridge these gaps sustainably?
2 Answers
Honestly, if you can solve problems effectively, you’re doing great! Things like kubelet details aren't make-or-break. Don't stress too much about trivia; Google is always there for quick answers. Focus on what you can do rather than what you don’t know!
It's a common misconception that most DevOps engineers have a programming background; in reality, many don't! You could start with small projects, like writing simple Lambda functions in Python or Go. This can help you get comfortable with the SDK and the software development lifecycle without needing a full-on coding career. Just pick a language and learn it at your own pace—it's all about gradually building your toolkit!
Exactly! If you can find answers easily, why worry? Retaining technical jargon isn't as crucial as actually solving real issues.