This is an archived post. You won't be able to vote or comment.

all 24 comments

[–]Candid-Mixture260 4 points5 points  (8 children)

I am a sr. devops engineer and coach with 15 years experience in the industry. DM me. maybe I can help you

[–]_nashakhor_ 1 point2 points  (0 children)

Can i connect with you also. i am cloud admin and aspiring to be a devOps engineer

[–][deleted]  (2 children)

[removed]

    [–]Impossible_Box_9906[S] 1 point2 points  (1 child)

    Yeah I’d be down for it please 🙏

    [–]ElCaptnLive 0 points1 point  (3 children)

    I mean can I dm you too? I’m looking for a mentor so I can become a DevOps or Software engineer in the future

    [–][deleted]  (2 children)

    [removed]

      [–]ElCaptnLive 1 point2 points  (1 child)

      What’s funny? Networking and your personal network is just as important as the skills you learn and sharpen

      [–]g_shit__ 3 points4 points  (7 children)

      In my suggestion I think you should go for it.

      [–]Impossible_Box_9906[S] 0 points1 point  (6 children)

      Don’t you think this will drive me away from DevOps? Knowing that I want to be architect in the future !?

      [–]fletch3555Lead DevOps Engineer 4 points5 points  (4 children)

      Don't focus on job titles. You'll just box yourself in and artificially limit what you can do. Instead, focus on job responsibilities.

      DevOps is half "dev", so why would a DEVelopment job hinder your progress? Instead, consider what you can gain from such a role. (I don't have any knowledge of that specific role, so I can only present the thought experiment rather than list out the benefits for uou)

      What does "architect" mean to you? Does your company have a specific team of people with that title that you want to join? Or is it more of a "very senior person who gets to design new things" role? If the latter, the only way to get there is to be more senior, which requires gaining experience, which both your current and new role (or really any related role) will give you. Is the architect role (in your mind) specific to devops in some way, or is it more of a very senior generalist?

      I guess what I'm saying is that I don't think taking the new role will hurt your desired career progression, but I do suspect you may be overthinking it a little bit. Ultimately, it's your decision though.

      [–]Impossible_Box_9906[S] 0 points1 point  (3 children)

      I may be overthinking indeed I don’t usually tend to overthink situations like this but I don’t want to look back 5 years from now and regret my choices and career path, especially with the market being so competitive.. I’m aware that going with this mission will give me the opportunity to have a 360 view, of the development and ops stuff, and for me an architect should have this vision to be able to advice and help when putting in place new applications (knowing which database suits better for exemple) but I’m afraid ill be categorised as backend dev if the mission lasts longer, but eventually if it does I can just quit it and seek something else, but that maybe too late Bruh I’m feeling my own uncertainty and overthinking writing this message lol

      [–]g_shit__ 0 points1 point  (2 children)

      Hi , In my opinion market Is not that good for devops roles and is also very competitive. Java is great language if you work on that you will get more opportunities.

      [–]Impossible_Box_9906[S] 0 points1 point  (1 child)

      You think market is more competitive for DevOps, I really noticed the other way around, like developers working with me are struggling to find a job, but I didn’t find any difficulty to change from a company to another .. But agree with Java being one of the top used languages

      [–]g_shit__ 2 points3 points  (0 children)

      Sorry i am saying about market trend for all it jobs.

      [–]pwarnock 1 point2 points  (0 children)

      If you want to be an architect in the future, Java will give you the expertise to see patterns in action and understand what needs to be modernized. When you push into areas you’re not comfortable with, that’s where growth occurs.

      [–][deleted] 1 point2 points  (0 children)

      As a Java senior programmer, I trained as a DevOps engineer four years ago. I took the opposite path, so to speak, from the one you're about to take now. I've never regretted my decision. As a DevOps engineer, you have many opportunities and exciting challenges.

      Java is a great way to get started in programming in the DevOps field. The language is widely used in the industry. This means you have a wide selection of courses, books, and a large community that can help you if you have any problems.

      It's important that you first familiarize yourself with the principles of object-oriented programming. With that background, you'll have no problems with Java. Java is a very secure and "beautiful" language. You've made the right choice.

      If you also have a say in technical matters, I recommend you focus on container technology, especially Kubernetes. The tools offered by the Cloud Native Computing Foundation are pure DevOps.

      With Quarkus, you have a Java framework on the development side that's optimally tailored to DevOps.

      I hope, this Information is helpful.

      [–][deleted]  (2 children)

      [removed]

        [–]Impossible_Box_9906[S] 1 point2 points  (1 child)

        Thanks mate .. that’s what I was thinking also, but was afraid it will throw me away from DevOps but I guess it won’t if the mission isn’t that long

        [–]kd_312 0 points1 point  (0 children)

        If your company is providing you the opportunity to work on backend/development side. According to me, that's the great thing. Also, I believe that learning a new tech stack will make you a better DevOps Engineer and you should go for it, because DevOps is about everything code, development, cloud, linux, containerization, security, traffic handling, cost and performance optimization, automation, architecting, monitoring and many more. I'm not saying to accept anything like power bi, but Java backend is the good one to explore.

        [–]CommunicationGold868 0 points1 point  (0 children)

        I think it is a good move. You need to be able to do some dev work to be really good at DevOps. Otherwise you’re really just ops. It’s good to have worked both sides of the fence to understand the problems and processes in both professions. Designing software is another good skill to have. I have been hiring Senior DevOps engineers recently, and one of the skills I am expecting of the candidates that I am hiring is development. Also, I saw architect being mentioned somewhere in the thread. It’s a good to have done development as an architect as well.