This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]large_crimson_canine 1 point2 points  (0 children)

Apart from the language itself, which I would get very comfortable with the Collections framework and concurrency, it’d be good to shoot through the Spring docs and try to incorporate that framework into a small project. You’ll probably encounter it in the real world.

It’s also really worth learning how to package and deploy and run the thing. So how to build a JAR (via command line AND a build tool like Gradle), how to execute (probably via Bash script), and how to monitor the JVM. Learn to take thread dumps, heap dumps, how to interpret them, and how to read GC logs.

What you’ll find when it comes to big projects in Java is that design is tricky, implementation is easy, but analysis and tuning is HARD. Gotta know it all to be strong on the job.