Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Whatever 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. -
For 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. -
@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
Need some opinions.
Imagine you’ve got loads of .net + angular under your belt. Like 10+ years.
A new place wants good software engineers from any background but their main thing is Java. So for their new work you will probably be writing it in Java.
Would you turn it down because by this point your specialised in .net.
Or would you be more ‘easy-come-easy-go’ about it and happily learn Java (not too hard) and all the surrounding libraries, toolset (I suspect this is where the effort would be)
I’m kind of of the opinion that switching to a whole other ecosystem might set you back. If you had to put a label on it I would describe it as going from being a senior to a mid-senior.
As you would fall behind with .net but still be trying to up skill in the Java toolset.
And it does feel a bit like learning Java at this point is like learning cobol.
Is my thinking wrong?
question