Hey everyone! I'm just starting my journey into DevOps, even though it's not my official role yet. I've been exploring my interests in Java and Android while working on a personal learning project. So far, I've dabbled in some basic Apache setups, built a simple pipeline using Jenkins, set up monitoring with Grafana and OpenTelemetry, and played around with automatic configuration using Ansible. I've also checked out a roadmap for DevOps and see that I still have some core areas to cover, like Artifact Management.
Right now, I'm trying to figure out what to do with my project. Here are a few options I've been considering:
1. Improve my frontend and deploy the app, despite it not being very useful outside of practice.
2. Wrap up what I've learned, make a summary, and maybe write a blog post about it.
3. Learn everything I need and then tackle a real-world problem with a new project, although I'm unsure how to find a problem that fits my current skill set.
I'd love your thoughts on which approach to take or any other suggestions you might have!
2 Answers
I think option 2 is the best route. Wrapping up what you've learned and putting together a demo along with a blog post sounds effective. After that, maybe you can see what interests you and approach option 3 later on by solving a real problem that grabs your attention.
Honestly, I'd recommend building up your GitHub as a portfolio instead. For someone just starting out, showing that you can use Git well and have clear documentation is crucial. Focus on making your repositories cover a wide variety of applications and deployment environments. This shows potential employers your ability to adapt and learn, which is key in DevOps. You can still write a blog, but many times, those can get outdated quickly because of how fast things change in the industry.
Got it! So I could incorporate good Git usage and documentation as part of option 2, right?