Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
h3rp1d3v468362dNever worked in Java. Most java code I witnessed in school looks disgusting and almost all schools teach Java. I hate Java
vintprox4806362dWhatever the looks of Java, you need to learn multiple paradigms to see the variety of their uses. Java is just that opportunity to hone data structures mindset.
What may be not sitting allright with potential learner here is that maintaining Java projects is a venture to legacy. You need to agree upon legacy, otherwise it's only a matter of week before you switch to another language.
hack6550362dFor me it depends on how they use java. Are they still using java 1.6? Is architecture beautifully designed? Are they using code quality analysis tools? What about tests? Code reviews? How they manage sprints and how tight are deadlines? Are they open for new technologies? (Like developing a new microservice in go) If most of the answers of this questions are better than your current job, I think its ok to change your tech stack.
Also your 10 years of experience in .net does not go anywhere. I have a friend that started his career with 5 years of .net, switched to java for 3 years and now he got a new offer for another .net position.
TrevorTheRat1176361d@hack I’ve not been able to formally talk to their technical people yet, but going by what the recruiter said they need people to bring work previously done by consultancies in house.
There’s some greenfield and some legacy work.
They don’t know for certain what projects and teams pistols will be placed on as priorities change.
So judging by that I would say the answer will be “every team is different”, with at best a mix of Java, node, .net versions and various degrees of bad to good architecture