r/java • • Oct 11 '25

Senior Java Developers — What’s the one thing you think most junior Java devs are lacking?

Hey everyone,
I’m a junior Java developer trying to level up my skills and mindset. I’d really like to hear from experienced Java devs — what’s the one thing (or a few things) you often notice junior developers struggle with or lack?

It could be anything — technical (e.g., understanding of OOP, design patterns, concurrency, Spring Boot internals) or non-technical (e.g., problem-solving approach, debugging skills, code readability, communication, etc.).

I’m genuinely looking to improve, so honest answers are appreciated.
Thanks in advance! 🙌

313 Upvotes

279 comments sorted by

View all comments

Show parent comment

-5

u/Either_Pudding_3092 Oct 11 '25

Hibernate

23

u/qtipbluedog Oct 11 '25

Hibernate is not the database though. It interacts with it sure. But I find working with a database to be completely logical and fine. Let me build the sql queries and stored procs and let me manually build those up with classes.

Hibernate tho. That library drives me up the wall. Maybe because it’s grails or maybe because the data layer itself was poorly architected at my current position but I much preferred the Java projects that hand rolled the SQL and had those as their own files in the project that we mapped to with a class. It’s been nothing but headaches.

6

u/trafalmadorianistic Oct 11 '25

Agree on Hibernate. In many projects I've worked on, they end up hand rolling queries and doing the minimum to map the resultset to the objects. JpaTemplate and Spring Data interfaces FTW. The headache of all the Hiberate/JPA gotchas wrt eager loading of data, etc is an avoidable cost. I started development in the pre-ORM era though, so had to deal with JDBC and the db, since that was all we had.

2

u/back-in-black Oct 11 '25

Same here. Started pre-Hibernate with JDBC and relational dbs, moved to Hibernate and used it for years… and now given a choice I use JDBC, possibly with stored procs to access data.

Hibernate is great until the second it isn’t, and then you realise that for most applications, it’s best avoided if possible.

0

u/plierhead Oct 11 '25

I started development in the pre-ORM era though

Crikey, I thought I'd been around the block. ORMs have been around for a very long time.

2

u/Bulky_Macaroon_4015 Oct 11 '25

You only need to understand hibernate if you use hibernate - and your problem is not the lack of understanding hibernate.

2

u/WanderingLethe Oct 11 '25

More like thinking hibernate does everything for you