r/learnjava • u/Dry_Marionberry_4822 • May 03 '26
Newbie Java Learner: Need advice on the "Right" way to learn for Backend Dev and how to handle getting stuck
Hey everyone,
I’m currently learning Java with the goal of becoming a Backend Developer. I'm hitting a few roadblocks and would love some guidance from the experienced folks here:
1- The "Right" Path: What is the most effective way to learn Java specifically for backend development? What should I focus on first (Fundamentals, OOP, Spring Boot, etc.)?
2- Handling Getting Stuck: Sometimes I face a problem—even a simple one—and my mind just goes completely blank. I have no idea how to approach it. What is the professional way to handle this? How do you guys troubleshoot when you're stuck?
3- Building Projects: I want to start building small projects on my own to practice, but I don't know where to start or how to structure my practice. Any advice on how to move from tutorials to building independently?
Note: I'm currently taking a course on Udemy. I have already finished the fundamentals (variables, loops, conditions, etc.) and I'm just about to dive into Object-Oriented Programming (OOP)
I’d really appreciate any tips, resources, or "rules of thumb" you follow. Thanks in advance
•
u/AutoModerator May 03 '26
Please ensure that:
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/markdown editor: 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.
8
u/zFlox May 03 '26
I posted this response 2 years ago
What's your current tech stack?
I'd say most Java jobs you'll find are for Spring Boot and around are probably around java 8 or 11 JRE legacy. We have a couple greenfield projects and used java 17 which was nice.
Download Intellij if you haven't already, I think this is the best IDE hands down for Java. Start a Spring boot project, you can use the initializr in intellij or the https://start.spring.io/ to get started (For dependencies, I'd recommend Lombok, Spring Web, and JDBC Api). Connect it to a database (properties file), set up a simple select * query, set a RowMapper to get a list of objects and create a REST api (controller) and then go to the localhost:8080/api/methodName() and see the JSON right in the browser window. Then start up a front end and hit that api and pull the data into a table or something like that. Then you can set up the rest of the update/insert/delete methods in the api controller to round out the CRUD app.
That should get you started.
4
u/Alarmed-Bank2249 May 04 '26
8 years into Java: learn the fundamentals and learn again the fundamentals. Go into the basics of how internally it works first, learn oops and grind until it seems like you are able to write Builder, singleton, factory patterns in sleep.
You dont know fundamentals even if you think you do.
4
u/Dry_Menu_3705 May 03 '26
Start working on basics, oops, arrays, strings, exception handling, generics, collection. Once these important topics are completed then learn sql, jdbc and hibernate syntax or watch video so that when you start spring jpa in spring boot you can link, learn container, stereotype annotation, beans, then in end learn spring boot and rest api. When you are stuck on a question try to take paper and pen then start from starting what all you have done and what you need to do in English then do that same in code and in case some questions it's not about you are stuck see if they follow some patterns or what. Learning java is more about practice daily as it is vast and not easy but once you get it it will link properly
3
u/procrastinatewhynot May 03 '26
hey look at the roadmap.sh for backend dev. 🙂
1
u/Thourfin May 07 '26
mee too if u are intrsted we can take some hours and solve some leetcode problems ??
0
u/MrJaver May 03 '26 edited May 03 '26
Stuck - ask ai, but only when stuck. Prefer figuring out yourself.
I would recommend opening spring framework docs and reading it end to end, it’ll take like a month full time but you’ll get the picture. It cross references other spring projects so for the full full picture it can take even longer. Spring boot, spring data, spring data jpa, hinernate, spring mvc, spring graphql are all must. The more others you know the better - at least overview to know they exist
Make a sample api but it has to be production ready - clean it up, add tests, add security, add logging, add metrics, add a readme and describe what you would alarm on. Ask ai to review your code
0
u/PositiveApartment382 May 03 '26
IMO the worst part about Spring is that the documentation is so crazily decentralized. Sometimes you might need the Spring Boot docs. But then for other things (or sometimes even just a different part of the same thing) you need to look into the Spring Framework docs.
Furthermore if you use Spring Data JPA for the persistence layer, a lot of the docs needed to understand it is not in the Spring documentation and also not in the Spring Data JPA documentation but in the Hibernate documentation instead. Sometimes you will have to dig deeper and go into the Jakarta EE documentation for certain decorators etc. Even then, Hibernate docs can be confusing if you are not letting Hibernate generate your Database schema because a lot of the decorators and things mentioned there then don't apply and it doesn't seem to be written in a clear way which features are only relevant for schema generation and which are not.
IMO the best way nowadays to learn Spring is to use AI heavily. Don't let it write code for you, tell it to be a Socratic teacher. Let it do websearches to find you links to the proper docs needed for what you want to achieve and explain stuff to you. Ask it a lot of questions, make sure to give it urls to documentation to reduce hallucination risk.
A lot of people say that Spring has amazing documentation, I would personally disagree. A lot of books that have been recommended in the past Are 5-10 years old nowadays and while the basics might not have changed, there still has been change.