Java coder, trainer, and coach. I love helping novices and experts write better, more testable code and have more fun doing it. I do corporate and individual (one-on-one) Java coaching and training.
I teach this stuff as a trainer, so I recommend becoming very familiar with how Spring does Dependency Injection (Autowiring), which means you'll need to have a good understanding of Java itself, how object references work, and how to use annotations. Also very important to become familiar with JUnit and writing tests.
As you've probably seen, the Spring Framework is very large, so make sure you're learning things that you'll actually need:
Will you be using databases? If so, which one(s)?
Are you doing back-end only, implementing Web ("RESTful") APIs, or front-end as well, using a template system to do server-side generated HTML, with Thymeleaf (hopefully not JSP)?
How/where are the applications deployed? And what is the deployment architecture: more like monoliths, a microservice setup, or somewhere in-between?
Once you've figured out the topics, then start creating a project of your own, with a focus on testability and figure out things as you need them using the Spring docs as a main resource, along with tutorials from the reflectoring.io web site (much preferred over Baeldung).
Thymeleaf maybe for testing only. As long as REST is in use, the native frontend should be developed. And while advising beginners don't mention microservice and stuff like that, please. And most important - there's no way to understand dependency injection without prior basic experience with plain Java. One can't notice the fundamental difference in those approaches if doesn't know both, especially how Spring benefits of Java Reflection.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I teach this stuff as a trainer, so I recommend becoming very familiar with how Spring does Dependency Injection (Autowiring), which means you'll need to have a good understanding of Java itself, how object references work, and how to use annotations. Also very important to become familiar with JUnit and writing tests.
As you've probably seen, the Spring Framework is very large, so make sure you're learning things that you'll actually need:
Will you be using databases? If so, which one(s)?
Are you doing back-end only, implementing Web ("RESTful") APIs, or front-end as well, using a template system to do server-side generated HTML, with Thymeleaf (hopefully not JSP)?
How/where are the applications deployed? And what is the deployment architecture: more like monoliths, a microservice setup, or somewhere in-between?
Once you've figured out the topics, then start creating a project of your own, with a focus on testability and figure out things as you need them using the Spring docs as a main resource, along with tutorials from the reflectoring.io web site (much preferred over Baeldung).
Wow! This is very insightful.
I will work on it step by step as you suggested.
Thank you very much.
Thymeleaf maybe for testing only. As long as REST is in use, the native frontend should be developed. And while advising beginners don't mention microservice and stuff like that, please. And most important - there's no way to understand dependency injection without prior basic experience with plain Java. One can't notice the fundamental difference in those approaches if doesn't know both, especially how Spring benefits of Java Reflection.