Why I'm Transitioning to DevOps/SRE: Building My Career in Public
Hey Dev community! 👋
I've just published the first post in a series documenting my transition to DevOps/SRE, focusing on financial services infrastructure automation. I wanted to share my journey with this community as I build my skills in public.
Why DevOps/SRE?
Several factors influenced my decision:
Technical Alignment
- Infrastructure and architecture over application development
- Automation over manual processes
- Systems thinking over isolated component work
- Terminal-based workflows over GUI reliance
Market Opportunity
- Consistent demand across industries, especially in financial services
- Resilience during economic fluctuations
- Emphasis on security and compliance expertise
- Remote-friendly work environments
My Learning Strategy
My approach centers around four principles:
- Project-based learning: Building real-world implementations
- Certifications as milestones: AWS, Terraform, and Kubernetes
- Public documentation: Articles about what I learn
- Specialization: Financial services compliance and security automation
Initial Focus Areas
I'm starting with these core areas:
- AWS Architecture Fundamentals
- Infrastructure as Code with Terraform
- Containerization Strategies
- Terminal-Based Workflow Optimization (Neovim, tmux, CLI tools)
Let's Connect!
Are you on a similar journey? Have tips for someone transitioning to DevOps? I'd love to hear your experiences and advice in the comments!
Follow along on my blog for detailed technical tutorials as I progress.
Image credit: www.freepik.com
Comments? Questions? Post below!
Top comments (0)