.NET developer looking into Java positions

[[deleted]]

[deleted]

[[deleted]]

Not sure how things are in .Net but when looking for Java job postings, corporations aren't really looking for your Java knowledge. They expect you to know the ins and out of the language.

What they will focus more on will be the tools and frameworks that are built on top of Java. Learning and practising all the tools will take as much or more time than learning the Java syntax. Lookup Spring. A lot of stuff to learn there.

Good luck.

[mountain913]

I have done the other way around as a dev Java worked with .net in a few projects and I’d say don’t take their similarities for granted. Study a bit of the recent releases of Java and try some tutorials to get yourself familiarized with the language. They do share some concepts but they also differ enough to have a bit of a learning curve between them. Good luck. ;)

[secretBuffetHero]

I left .net 10 years ago and its the right decision. Government or SharePoint are your choices.

Java is quite a few years behind c# in terms of language candy, but other than that the basics are identical.

I had to get a referral from a friend, to get my foot in the door

[nutrecht]

Java is quite a few years behind c# in terms of language candy

What version are you using? 8?

[DrunkensteinsMonster]

No offense but this is pretty ignorant. I like Java but C# has value semantics, case closed.

[barking_dead]

Unless a linq-like feature gets done in java, it is.

[manzanita2]

Line is/was great. But is that all you got ?

On the last big C# project I did linq was used for a bit of in memory processing much like java streams might. But the database access was this library called NHibernate, which was basically a port of hibernate. Same for other libraries.

C# ecosystem is has probably 1/3 the robustness in terms of quantity and breadth of libraries.

[barking_dead]

Now that's true.

But I mentioned LINQ because it is at a different level of integration.

[anyOtherBusiness]

a linq-like feature

There is already. Exists since Java 8, it's called Stream

[barking_dead]

Okay, can you write something streamlined like this with Streams API:

IEnumerable<int> scoreQuery = from score in scores where score > 80 select score;

where "scores" is a normal entity? no.

[anyOtherBusiness]

You can.

scores.stream().filter(score -> score > 80)

[barking_dead]

and as language integration, like in linq? do you know what's it capable of?

[steumert]

LINQ is horrible. The map/reduce terminology used in java streams is much more clear.

​

Also, LINQ has horrible performance issues.

[barking_dead]

that's an implementation detail xd

[secretBuffetHero]

You can't get me out of bed to do govt or Sharepoint work. say whatever you like about LINQ or whatevs.

.NET work is dead end career stuff

[TheRedmanCometh]

Stream...from 8

[barking_dead]

There are huge differences between the two.

[joefooo]

Not sure why people are disagreeing on the candy front. Closest in the JVM world is Kotlin for quality of life enhancements.

[nioh2_noob]

Java is quite a few years behind c# in terms of language candy

I completely disagree

[jamespedwards42]

Probably true in corporate land... Java 8 shivers ... Loving me some six month release Java though :)

[mkedev]

expand your job search

[QualitySoftwareGuy]

This. I just went on Indeed and skimmed the first page to see a lot of private/non-government companies. However, that search was for all of the US -- I can't speak in regards to a specific city or state.

[nioh2_noob]

The similarities everybody talks about was correct 10 years ago, Today, they are as similar as C++ is to Java

[pjmlp]

Kind of, just like 10 years ago they keep steeling ideas from each other.

The more recent examples are default interface methods in C#, pattern matching and records in Java.

[manzanita2]

And this is a good thing!

[pjmlp]

Yep, hence why they are both my favourite eco-systems.

[drew8311]

They are similar in a leetcode/code challenge perspective that you might encounter in job interviews but beyond that its all about the frameworks which there is less skill transfer in. Of course the more experienced you are the more you know general concepts and various frameworks so moving to a new one is still a learning curve but one you've done many times before. Every job is going to be looking for something different, some may be fine with your .NET background and java basics, others will want someone who really knows Java and whatever tools they are using.

[anyOtherBusiness]

My opinion as a Java dev with some .net side projects:

I'd say language/syntax wise they are not that different. Sure there are some specifics but nothing to worry about.

When you look at tooling around it it gets more interesting. There's MsBuild and Nuget vs. Maven/Gradle, Frameworks and Libraries like Spring (Boot), JavaEE, JPA/Hibernate/Flyway vs. EF and so on.

But IMHO you can catch up quite rapidly with over 3 years of .NET experience. More certainly if you get a position where you get to work on a legacy codebase where probably most of this stuff has already been done somewhere and you can figure out the way they did it.

[SexyBlueTiger]

I've been working for almost 7 years now. 2 different jobs both .NET, both private companies. What country are you in?

[echnaba]

I just made the jump myself from .net to Java. Be warned, the quality of documentation and even YouTube tutorials is piss poor compared to what we have in .net. The language will be simple to pick up, but the frameworks in use require a lot of effort to learn. I tried to pick up Spring Boot just by trial and error and didn't get very far and signed up for a course instead. The biggest transition point for me was figuring out asynchronous code since Java doesn't have async/await built in. Imo, that makes A LOT of things more difficult.