I started exploring DevOps recently, and honestly, it’s been eye-opening. Coming from a backend background, I always focused on building APIs and features. But now I’m starting to understand what happens around the code. So far, I’ve explored: • How the Software Development Life Cycle actually works • Where DevOps fits in the bigger picture • Basics of project management • Working with Virtual Machines • Launching and managing instances on AWS EC2 • Using AWS CLI • Linux fundamentals + shell scripting • File permissions in Linux • Version Control with Git & GitHub Still early, but things are starting to connect. Next week, the plan is simple: → Deploy a Node.js app on AWS (end-to-end) → Get hands-on with Infrastructure as Code (Ansible & Terraform) Trying to move from “I know this” → “I can actually use this in a real setup.” If you’ve been down this path, I’d love to hear — what should I focus on next? #DevOps #AWS #Linux #Backend #LearningInPublic
Great direction. One thing that really accelerates learning at this stage is focusing on end-to-end ownership — not just deploying, but adding monitoring, logging, and failure handling to your setup. That’s where DevOps starts to feel real.
That shift from writing APIs to thinking about infra is the real jump. Once you automate the setup, everything starts feeling different.