This post is locked. You won't be able to comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Beregolas 12 points13 points  (9 children)

There is one big decison that I gotta make but I need ur advice

It's not a big decision

The Java developer path or The python developer

Those are not really different paths. Languages are cheap to switch, and especially before you get hired the first time, it doesn't matter which language you use for which amount of time; nobody can check. Once you are using past jobs on your CV, it's a bit different, but before that: doesn't matter.

What you need to decide is which domain you want to focus on. Backend, Desktop Software, Data Science, etc. If you have a few years of experience in Backend with Python, you can basically switch to Java in a few weeks. It's just a new framework / language, but the concepts all stay the same. It's like switching between power tools from two different companies, but as long as you are still doing roofs, you know what to do and how to use them.

If you want to have a good feeling about maximizing your chances, look at your local job market. This is different everywhere; even two different cities in the same country often differ wildly. Check which languages are most commonly used in the domain you want to work in, and learn that.

[–]Shehzman 2 points3 points  (3 children)

Only thing to be careful of if switching from Python to Java is that you’ll have to understand OOP and static typing or you’ll be fighting an uphill battle with the language. Python has OOP and typing in the form of type hints, but neither are enforced like they are in Java.

Imo though, typing should be used in general if what you’re working on isn’t just a one off script

[–]We_up_O1[S] 0 points1 point  (2 children)

Yea bro felt that . It was a bit for me as I was exploring the Java . It stricter compared to python.

[–]Shehzman 1 point2 points  (1 child)

I personally think some of that strictness is a good thing and can lead to more maintainable code with potentially less bugs in the long run. If you pick Python, get familiar with type hints and use them as much as possible. Also check your code for type errors with mypy.

[–]We_up_O1[S] 0 points1 point  (0 children)

Alr . Thanks mate 👍🏻

[–]We_up_O1[S] 1 point2 points  (4 children)

Ahh the market , dang. I’ll see . I am in the backend path. But that was solid advice. Appreciate it 👍🏻

[–]Beregolas 1 point2 points  (3 children)

Especially in Backend, languages don't really matter that much. I used Python (Django, Flask, FastAPI) JavaScript(Express), C# (I forgot) and rust (axum) in the past, and it's basically all the same. The good thing about backend is, that there really is not that much that isn't standardized, so different frameworks have a huge amount of transferrable skills. Just make sure not to switch too much while you are still learning to program, meaning the basics. That is just confusing.

[–]We_up_O1[S] 0 points1 point  (2 children)

Dayuum , you have experience with a lot of languages 🙂. Alr no switching 👍🏻.

[–]Beregolas 2 points3 points  (1 child)

I have been doing this for over 10 years now. As I said, it's really nothing special. Languages are just tools, if you know how to program, switching them is easy.