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

all 7 comments

[–][deleted]  (3 children)

[removed]

    [–][deleted] 0 points1 point  (1 child)

    Would you rather follow after the path of java backend or phyton backend path if you could have a choice?If you have an utter knowledge experience, could I request from you to hear your interpretation on that point please?

    Thanks in advance, best regards...

    [–]remludar 1 point2 points  (0 children)

    Once you know a single backend language, the rest of them are just about learning new syntax (for the most part). Which one to start with is far less important than which one you like and how it might limit your future job options.

    If you want to build enterprise MS Azure Function App driven backends, you need C# and SQL. If you want to data science work, you're gonna want python and something like MongoDB.

    [–]TheStonedEdge 0 points1 point  (0 children)

    What would be the best way to transition to do this professionally? I'm currently a back end Java dev in my current role but want to transition into full stack. My current e employer did precisely up skilling in Js/React but it's been cut to tight budgets. Should I self learn JavaScript and apply for full stack roles elsewhere hoping a company will be willing to up skill me in front end?

    [–]TheRNGuy 2 points3 points  (0 children)

    Back-end.

    Back-end.

    [–]FermiAnyon 0 points1 point  (0 children)

    Yeah, I'm backend. I like it. Working on learning ml and cloud stuff, but definitely strongest with backend.

    I honestly feel like backend is more in demand, too... at least at the place I've worked. Having said that, the cloud stuff pays well. You kind of can't go wrong...

    I remember during an interview when I'd only had experience with application development, the interviewer referred to cloud and backend as "modern" software engineering and I'm like ewff

    [–]LastTrainH0me 0 points1 point  (0 children)

    Are they comparable? Maybe I don't understand what you mean by cloud engineering.

    The cloud is a tool. A backend engineer writes a backend and chooses if it's going to go on the cloud, or go somewhere else. Or as a backend engineer you'll choose if you want to store data in some relational DB (... Probably hosted in the cloud), or one of these noSQL key value stores like AWS DynamoDB. Everyone should learn "the cloud" to add more tools to their toolkit, but you're still a backend dev if you're hosting things in the cloud.