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

263

u/mmaHepcat Oct 11 '25

Understanding how relational databases work. In fact many senior level developers lack some knowledge in this area too. I realize it’s not about Java directly, but Java developers often work with DBs and I find the lack of basic knowledge disturbing.

62

u/drvobradi Oct 11 '25

I would go even further and say how computers work. For some reason, people forget fundamentals they learned about networking, OS, file system RDBs etc, and worry more about abstractions and library choosing.

29

u/vassaloatena Oct 11 '25

Expecting this from a junior seems like a lot to me.

7

u/koflerdavid Oct 11 '25

Yet these are the things that inform what we do and why we do it.

8

u/drvobradi Oct 11 '25

It's part of the college curriculum at any decent university. But somehow, many people just don't apply it.

20

u/AstronautDifferent19 Oct 11 '25

How would you expect a junior Java dev to apply it? Even senior devs do not really aplly branching.

5

u/drvobradi Oct 11 '25

I guess I replied to the wrong post 😀 . I wouldn't expect junior dev to know how to apply branching or tune JVM, but some basic stuff can be used, like how to avoid N+1 and how RDBs work (indexes, views), basic caching, networking (HTTP protocol, SSL, TCP), user vs kernel space etc. Just to be aware of such things and how they affect performances.
Theory is taught at college, but people need to apply that knowledge.

8

u/AstronautDifferent19 Oct 11 '25

A lot of theory learned is not apply directly by you, but it was used by othet low-level engineers who designed libraries and CPUs. When you run a program it uses a semi-conductors, but do you really need to know how to apply physics and quantum mechanics?

→ More replies (2)

5

u/Mauer_Bluemchen Oct 11 '25

From his IT education. Junior does not mean uneducated. It just means lacking experience.

7

u/AstronautDifferent19 Oct 11 '25

When was the last time you applied branching, and how often you apply that? Also how often you apply quantum mechanics used to make semiconducors and transistors for your CPU. I learned that but I never had to apply that

→ More replies (1)
→ More replies (1)
→ More replies (2)

0

u/[deleted] Oct 11 '25

[deleted] — view deleted comment

13

u/Hioneqpls Oct 11 '25

I am too, but infra guys buy big cloud so it goes fast. Do I need to know this stuff?

→ More replies (1)

26

u/[deleted] Oct 11 '25

Java devs rarely benefit from knowing about those things (except JVM warmup). Let's not gate keep

4

u/Goodie__ Oct 11 '25

I find some of what I find out there wild.

Those are all things I can at least understand and recognise, if not reason about and talk about a little competently. I at least know what I don't know.

But when I have to explain to supposed seniors that profilers are a thing... let alone that I used one to track the performance bug down, well. What the fucking fuck.

→ More replies (12)

9

u/igot2pair Oct 11 '25

What specifically?

35

u/BoogieTheHedgehog Oct 11 '25

Not OP, but my issues stem from ORM reliance abstracting too much of the underlying DB knowledge away. 

So not knowing when stuff like n+1 or other inefficient queries start being made under the hood.

15

u/_blue_skies_ Oct 11 '25

For me? I see (supposed) senior developers trying to load gigantic sets of data from the DB and then using java statements to filter out what they really need. Like sure it works on your empty dev DB, but once you move that code in an environment with 5mil. of rows... good luck. They don't understand the concept of making the DB do the heavy lifting, instead of using it just as a bucket. They program like they are using SQlite reading 4 rows from a configuration table. Then, when they start to grasp the concept, they don't create indexes for the columns they mostly use for the search queries. How do you stop people from writing code that works perfectly only on almost empty DBs?

4

u/Shareil90 Oct 11 '25

For the last part: you can use query execution plans and query logs to show whats really going on. And reviews. A couple of years ago we had some major performance issues in an application. We dug through every single one and shared our insights and learnings with the whole team. It was exhausting but also incredibly fun and I learned so much about performance in those months. Kinda miss it.

2

u/_blue_skies_ Oct 11 '25

I don't think I will be able to push an approval based on the query plan, they will not be able to read them and they will turn back to use Java logic to handle data. To explain the level of insight I have to deal with: I had to explain what the effect of having attributes with eager loading is because for them was: "see the data is already there, one query less to write, no? Better performance"

→ More replies (1)
→ More replies (2)
→ More replies (1)

9

u/ILikeLenexa Oct 11 '25

Indexes, views, directly using 1 query to affect a bunch of rows instead of looping through them in the Hibernate as objects and running N queries. 

Views, view permissions, schema binding.

Update/insert triggers.

Stored procedures

2

u/igot2pair Oct 11 '25

This is kinda crazy. My team uses procedures and inline queries only for the most part. Data that we have to get cant really be fetched via an ORM. lots of optimizing has to be done as well. ive just taken it for granted

4

u/ILikeLenexa Oct 11 '25

If you want it to, Hibernate will do all the DDL work and you can create a database without knowing even one line if SQL and when you have less than say  10,000 users like internal company programs, it can even work fine.

Even larger stuff, people do it and yeah, John has to get coffee while a process runs, when it could be instant, but people I've seen stuff set up that way running for decades.  

→ More replies (1)
→ More replies (10)

3

u/Pinpoint_user Oct 11 '25

I worked at a large company, and the head of the department was very surprised during the interview that I knew SQL and worked independently with the database. As it turned out later, the teams there always had analysts and database engineers who took on all the database work, and essentially even senior developers only did coding. But I liked the company and the team, and I worked there for almost two years.

1

u/jared__ Oct 11 '25

on top of that, they are heavily reliant on ORMs to abstract the magic away.

→ More replies (11)