Ask HN: How does one get into Java EE in 2022?

3 points by kakadu ↗ HN
Is there a knowledge path?

9 comments

[ 2.8 ms ] story [ 28.3 ms ] thread
What are you actually trying to do? Build your resume? Or build a specific technical thing?
Can't speak for the OP, but in my case I'm curious to see how to transition from self-taught Ruby/Go/devops/polyglot/* into hireable in enterprise java engineering roles without going back to school for a CS degree. There's no time or budget for that in a down economy in my case (not realistic). Is that even possible, and if so, what might the recommended way forward be? Certifications of some kind? Which ones are actually respected, if any? What are interviews like in that world?

I'm coming at this from a lens of "I'm tired of getting laid off all the damn time". Java seems to still be going strong economically/job-availability-wise despite its faults/criticisms after all these years, may as well get on the bandwagon for a 9-5 so I don't get laid off every so often and have to re-skill with the latest new shiny to win "flavor of the month" all the time.

Haven't decided this is THE one and only "one true path" or anything, just exploring it and wondering if this is even viable coming from where I'm at right now. To answer that question, I'd have to know how to get from where I am to where I want to be.

I haven't yet personally encountered self-taught folks who ascend to the niche of enterprise Java and excel at it. I'm sure it's possible, but I suspect it's a difficult path.

Java is manageable compared to C++, but a big nasty beast compared to Python, Ruby, Go, etc.

I think even in a down economy, a CS education is a good investment of your time. These days you can even do it online, and getting grounded in the fundamentals is a superpower when properly leveraged.

I was about to post a similar Ask HN myself earlier today but got sidetracked. Thanks for putting this up, I'd like to know too!
Honestly curious, why would you want to? If i was starting from scratch, thats like the least appealing ecosystem imo
My advice would be to focus on servlets deployed into an embedded Jetty instance within your server, and that's about it!

The other parts, like Session and Entity EJBs, JMS, Java Server Pages, SOAP, SAR and WAR packaging formats, JNDI etc. etc., have long ago been supplanted by much better technologies.

and JDBC too.

Why servlets instead of Jetty handlers?

JDBC definitely. I didn't mention it because I didn't think of it as part of the Java EE spec (JDBC preceded Java EE if I'm not mistaken).

As far as Jetty handlers, they might be a good alternative to servlets. I admit I'm not familiar with the details.

Go work for old banks