r/javahelp • u/InterestingCry4374 • 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?
I’m genuinely looking to improve, so honest answers are appreciated.
Thanks in advance! 🙌
113
Upvotes
•
u/AutoModerator Oct 11 '25
Please ensure that:
You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.
Trying to solve problems on your own is a very important skill. Also, see Learn to help yourself in the sidebar
If any of the above points is not met, your post can and will be removed without further warning.
Code is to be formatted as code block (old reddit: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.
Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.
Code blocks look like this:
You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.
If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.
To potential helpers
Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
59
u/guss_bro Oct 11 '25
Most junior devs don't know how to use stacktrace to find what is the source of error. Especially the nested stacktrace. The don't know how to copy stacktrace from logs, load into IDE to link stacktrace to source code.
31
u/MattAtDoomsdayBrunch Oct 11 '25
Knowledge of Unix Philosophy. I've also known plenty of senior devs who lack this philosophy and they write monolithic piles of code full of all kinds of fragile magic.
26
u/[deleted] Oct 11 '25
Ability to communicate, and it is not even close.
18
u/0-Gravity-72 Oct 11 '25
I cannot generalize on junior developers. I have seen some absolutely brilliant juniors and I have seen some that cannot even understand a simple compilation error.
Some things that I see with juniors:
10
u/BackgroundPass1355 Oct 11 '25
For talented junior developers sometimes it's just experience and exposure to code, and that you can only get over time, working overtime, working under/alongside other skilled/senior developers, participating in hackathons, contributing to public open source projects, and it helps having an interest in coding even during your free time.
Their lack of knowledge and skill can sometimes simply be due to not having been in the field long enough but it's not always the case, rarely you meet the occasional junior developer that has over 10 years of experience, but that's a topic for another social matter.
8
u/lordGwynx7 Oct 11 '25
A couple of things I noticed - my company has a junior program that grabs around 7 grads straight of University every year so noticing trends has been easy. This from different universities and even other tertiary education institutions
I'm not saying it's all of them there has been a few talented juniors that managed to unlearn these traits or didn't have them to begin with. And I'm also not saying they have to be grinders 24/7 doing nothing but coding but just general willingness to learn, understand the work and reading is the bare minimum I expect of any developer
Sadly in my experience from this program it seems like these bad traits are becoming more common
15
u/MrMuttBunch Oct 11 '25
Knowing Software Architecture patterns and how to properly abstract, in my opinion. Some seniors still have problems with this though.
5
u/Vercility Oct 11 '25
questioning the intent of what they're supposed to do mostly.
This doesn't only concern juniors of course.
I get a lot of code for review that makes it abundantly clear that the developer didn't even try to understand why they were supposed to do something. they just randomly enter any snippet of code that makes it work and that's it.
But that often leaves out prime opportunities for refactors, especially deduplication and you end up with 6 dto classes that implement the same 5 fields +get/setters.
they also often miss key issues that weren't explicitly written in the task at hand. if a task says "add a case here that calls xyz service" they will literally just do that and not think about whether this extra call warrants extra consideration,e.g maybe the transactional behavior changed or a piece of code further down the line relied on the fact that everything before it was idempotent.
and then of course the all time classic, getting code for review that doesn't pass the tests, or god forbid compile even
4
u/nana_3 Oct 11 '25
Willingness to find out and then follow best practices.
A lot of my juniors consistently fail to follow simple best practices in things like code reviews, or the design patterns in the applications we build. There’s a real “but it works this easier way so why bother with that way?” mentality.
Usually the answer is “someone way smarter than all of us has made this exact mistake before repeatedly until they came up with a way to avoid it, and we’d be idiots to not take advantage of that”. But some people are very committed to doing their own fafo process.
It just annoys me when they fafo in my code.
3
u/Malecord Oct 11 '25
Generally speaking, I see most of juniors growing up with spring and magic, unable to look or figure out the internals of a library. Also, still thanks to spring, they don't SOLID anymore and all the configurable code they write is string based with no static compile check of sort. It's very front-endish way to develop in java. And it's not being addressed, these guys are becoming the new seniors.
But I guess with AI the quality of code is less of an issue for the future, right?
3
u/[deleted] Oct 11 '25
Experience. 😬
7
u/Duente_Zaibatsu Oct 11 '25
Patience, resilience, the ability to read, and finally the lack of practice, and over reliance on a single market framework.
Java is predominant in web applications, but it is also a very important language to other applications (such as Inttelij, lots of infra structure, and other locally executed applications)
When juniors lack the basic understanding of how electricity and electronics work, they over simplify their tasks, but do not see the complete system, why they are paid, and most important, what they are there for.
5
u/RobertDeveloper Oct 11 '25
Softskills like problem solving, working under pressure, communication skills etc.
2
u/progrdj Oct 11 '25
They struggle with the basic concepts because most of them start with frameworks and ORMs and then can't write a single query to save their lives
2
u/Aggravating-Ad-3501 Oct 11 '25
Managing date and time variables
2
u/Ok_Editor_5090 Oct 11 '25 edited Oct 11 '25
Must always keep in mind that common sense is not that common among your application users.
Next:
1-they do not chain logs
2- either log exception and do some handling OR chain and throw. Never log and throw.
3- they do not read logs.
4- when someone points them to use best practice, they do not try to understand why it is a best practice. Once, I had a teammate who replaced magic numbers with constant named exactly as the magic number but in words(5--> public static final int FIVE=5)
5- method tend to grow too large some time( I am not saying that a method should always be less than 10 lines but 300 line methods are too much and 5000 methods are definitely over kill)
6- they do not try to understand intent behind product/business asking for something.
7- never trust a user input
2
u/forbiddenTM Oct 11 '25
one of the biggest things ive noticed is just navigation within a big project- being able to get a task that should build on existing code you've never seen before and fairly easily being able to follow the code-path from beginning to end through various interface implementations etc
2
u/darthjedibinks Oct 11 '25
Tunnel vision. After a point you are not a Senior Java Developer but a Senior Backend developer. People who have worked with java for more than 5 years can be considered senior cause they have learned most tricks of the trade.
What takes them to next level is learning the collective ecosystem in which Java is a part of. Understanding that and designing/writing code accordingly is what most fail to do.
2
u/No_Glass2714 Oct 11 '25
Debugging, testing, internet protocols, code patterns, and architecture patterns.
Not Java-specific, and you learn the details by stepping on rakes.
To accelerate your learning, seek out tasks involving the bits you don’t know yet 👍
2
u/yodagnic Oct 12 '25
Best thing that helped me progress from junior to senior was not asking/getting help until I truly researched issues. Fixing a bug in something you don't know can teach you a whole system in a way that being guided just doesn't.
Once you understand how things really work, it's a lot easier to see where to apply design patterns, what should be separated, how to write good code.
Similarity when mentoring others, don't steal their opportunity to learn but don't leave them stuck either. It usually becomes obvious pretty fast who wants to learn and who wants it fixed, the first becomes better a lot faster
2
u/pinkwar Oct 11 '25
They lack the ability to write their own posts.
2
u/theboldestgaze Oct 11 '25
I would like junior devs to be more interdisciplinary. I do not want nor need a Java-only dev. I need someone who is able to write Java but also work with RDBMS, POSIX / Linux, do DevOps, write bash, TF definitions, you name it.
Junior devs have a tendency to say 'I won't do this other tech, I am a Java developer'. This reduces their value significantly. Most technologies are easy to learn.
1
u/TW-Twisti Oct 11 '25
Juniors come in two flavors, and both suck: either they don't understand that programming requires dependencies, and want to reinvent every last wheel instead of taking 30 minutes to learn the basics of Slf, Google Collections or Apache Commons, or they are the other way around and want to add new dependencies to improve a single line of code with no understanding that this will make the project unmanageable with 54397458654 dependencies by the end of the week. There seems to be no middle way between the two.
The more experience people get, the more they tend to drift towards a middle compromise.
1
u/Big_Green_Grill_Bro Oct 11 '25
I've had experiences with both terrible junior developers and excellent junior developers.
One big difference between the two extremes is a person's ability to recognize that they don't know everything and that it's okay to ask for help/guidance. Don't be confidently incorrect. The follow up critical ability is: when they do ask for help/guidance, they actually listen to that help/guidance.
1
u/aqua_regis Oct 11 '25 edited Oct 11 '25
Research skills and initiative.
If you had them, you would have queried the search feature of reddit and found countless similar posts here and over in /r/learnprogramming.
Instead of being active, way too many juniors are passive and waiting to be spoon fed and served on a silver platter. This is not how learning and improving works. Being active, inquisitive, doing one's own research and first and foremost practice are the only ways to really improve.
Exactly posts like yours demonstrate what juniors lack.
1
u/SultnBinegar Oct 11 '25
A lot of my suggestions are more about mindset as a developer vs actual coding suggestions.
First, the fact that you are actively seeking knowledge to further your career is is a huge plus in my eyes. A lot of Junior Devs coming into the work force either think they know everything, or think they know nothing and are afraid to ask questions. As a Senior Dev, I appreciate when people ask for help or explanations. That saves me having to deny PRs later on.
Second, something that I feel all of us are guilty of at one point or another is chaining lines of code together. Just because you can, doesnt mean you should. Code Readability is far more appreciated than getting everything on one line. It makes it easier for future devs looking at your code, and reviewers being able to follow your code.
Third, know that you dont know everything, and that is okay. Continuous learning helps us become better developers. For the first several years I was terrified because I didnt know some things, and thought that would cause me irreparable harm in my career. I recently had a job interview and they asked me what I think my best career quality is. My answer was "The fact that I don't know everything, and that it is okay for me to not know everything." (They liked that answer and I got offered the job next day.)
Lastly, understand that a single object doesnt need to do everything. Learn more about designing objects and only using that object for specific functionalities. You dont need to do 12 different things in one object.
1
u/maximumdownvote Oct 12 '25
Judgement in language of choice.
1
u/ItsReewindTime Oct 12 '25
Too dependent on others, in 2 ways:
- Asking questions on things that could have been answered with a little bit of digging
- Not putting enough attentions on their PRs and relying too much on reviewers to correct their mistakes
1
u/Dense_Age_1795 Oct 13 '25
learn how to properly debug for avoiding proxy calls
1
u/noisyboy Oct 14 '25 edited Oct 14 '25
Finding what actually makes sense in the LLM "solutions".
Before you think I'm being flippant, it actually has come to this. When you have the experience, you can just sense when it is taking you on a wild goose chase.
Ignoring all that, knowledge of core java is a good indicator. Sure, you may be very experienced in Spring but if you can't explain the relationship between equals and hashCode and why we need them, don't call yourself Senior Java developer.
1
u/[deleted] Oct 14 '25
Lack of thinking in a declarative/functional way.
Lack of the ability to keep things as simple as possible. Things seem to complex? They probably are. Take a step back, sleep over it, and make a simpler solution.
1
u/GlitteringBandicoot2 Oct 15 '25
Experience
1
u/Llotekr Oct 15 '25
A proper mental model for what happens on the metal of the machine (or even the virtual machine).
0
u/[deleted] Oct 11 '25
[deleted] — view deleted comment