ALL IN ONE! Java + Spring Boot, Spring and Hibernate [NEW]

too slow, she types slowly and we have to wait for her typing, half of the video is her typing and then one line of learning. in 18 minutes of video learning is just one minute 17 minutes is her typing.

One star because I learned something. Second half one, because one star means "Not what I expected at all" and that would be too low. Why not more? 1. This "ALL IN ONE!" course is not a course conceived to be an all-in-one course. It is a bunch of other courses, glued together into a single course. 1.1. In the first section, Eclipse IDE is to be installed and then used. Starting with section 6, instructors start using IntelliJ IDE. I personally have no issue with it and stuck with Eclipse. However, participants with no previous experience in IDEs will get in trouble. 1.2. A lot of content is repeated. The 32h 28m of videos could easily be reduced, or additional topics could be added. 1.3. A course like this one would be a great opportunity to build a full E2E application. But due to the fact that at least one new project is started in every section, instead of extending the existing one, this opportunity is lost. I know (because I did so) that working with a single project throughout the course brings some additional challenges. Nevertheless, I learned a lot by doing it that way. 2. In most of the lectures, the instructor refers to the "Resources Section". But resources are nowhere to be found. As a consequence, there is a lot of additional typing to do. I asked Sunshine Coding where I could find these resources, but never got an answer. 3. Missing topics in this course: 3.1. In the Hibernate section: a master-detail data model, like invoice and invoiceline table. No application has stand-alone tables. 3.2. In the MVC section: the most basic use of a checkbox, namely binding to a boolean. 3.3. In the MVC section: using an Enum or HashMap for the items in a select or a radio-set. 4. The concept of this course is the old-fashioned, boring classroom training concept transferred to video. 5. The endless whiteboard (just a fancy replacement for PPT): 5.1. The gifs at the end of the lectures are as non-professional in the endless whiteboard as they are in PowerPoint. 5.2. Typos in prepared course materials are unacceptable. 5.3. Using that marker on the whiteboard is bothersome. I can read along. 6. Code: the majority of the code written in the courses would not pass any code review. Independent from the coding guidelines and naming conventions one encounters, there are some basic principles that always come back. 6.1. Code should be well structured. In Java, this means for me: always use packages. 6.2. Give meaningful and correct names: 6.2.1. Naming a controller class just "Controller" is bad practice! 6.2.2. Naming a class, which is not a descendant of the Exception class, "EmployeeNotFoundException" is bad practice! 6.2.3. Defining a collection of cars as "List car;" is bad practice! And then looping through the collection with "for(String myCars: car)" makes it even worse. 7. Instructors: 7.1. On a few rare occasions, they say things that are plain wrong. 7.2. They generally work very inefficiently. 7.3. Small details, but after what feels like hearing it a thousand times, it gets annoying: 7.3.1. Query is pronounced ˈkwir-ē or ˈkwer-ē NOT ˈkwī(-ə)r-ē. 7.3.2. The correct expression is "What it looks like" or "How it looks", NOT "How it looks like".

This was most definitely what I was looking for, although most of the things I have learned through YouTube but YouTube doesn’t cover in depth what this course teaches. I started my Java journey from Data Structures and Algorithms and the fact that this course covers the basics, it’s just perfect to an absolute beginner who knows nothing about programming.

Great