Hey everyone! I'm reaching a Senior level in my field, and I've noticed that having architectural knowledge and staying informed about trends is becoming more crucial. I've read the DevOps Handbook, followed some resources like ByteByteGo, and know where to look for interview prep, but I want to go deeper. At my current job, we're moving towards a modular design for self-service products and adapting a GitOps strategy with tools like ArgoCD and Terraform, plus we're considering the latest trends like IDPs. I'm happy with the tools and implementations, but it feels like I'm learning a lot from my colleagues rather than through dedicated reading or research on my own. I know every company has its own challenges, but I'm curious about how you all keep current with new methodologies and how to think critically about them. Would love to hear your suggestions!
5 Answers
I tend to scroll through Hacker News to see what's buzzing. The CNCF Slack has channels that can be insightful if you can filter out the noise. And talking to other engineers has been invaluable; we do monthly deep dives into new ideas. It’s a great way to learn from their experiences too!
Make sure to check out the Thoughtworks Tech Radar regularly. It’s a decent resource for staying updated on technology trends and methodologies!
It's great that you're willing to learn! Subscribe to some newsletters like DevOps Weekly or ByteByteGo. Attend KubeCon or DevOps Days to get insights from talks. Also, building your own knowledge base can help you think critically about trends. What’s a trend you’re really interested in?
Watching the Linux Experiment channel has really helped me keep up with Linux news. I had an incident last year when virtual environments for Python broke our pipelines, but since I had learned about it from the channel, I could lead our meeting and suggest a fix!
Instead of just following tool news, I focus on principle-based sources like CNCF blogs and long-form writeups. They help build a foundational understanding of why trends are happening, not just what they are. Understanding context can make a big difference!
I've been focusing on GitOps lately, especially with how it's evolving!