Code review. 4
This time, the code review was for a fairly large project. Therefore, instead of using the standard GitHub pull request tool, we decided to download the code locally and perform the code review using the IntelliJ IDEA IDE. The process itself began at the controller level, i.e., from the bottom up. However, typically, if pull requests are small (as they should be in practice!), it's better to perform code reviews from the bottom up, starting with database analysis and entities, and moving up through the n-tier architecture.
Throughout the video, I've used best practices I've learned from my many years of experience, as well as the experience, sweat, and blood of hundreds, even thousands, of other programmers. Therefore, it would be great if every Java developer adopted these best practices on their own projects, thereby raising the quality and standard of software development in general.
Link to all my courses:
https://taplink.cc/denis.dmdev
30 BEST PRACTICES IN JAVA:
https://t.me/DMdev_mainBot
GitHub project with video:
https://github.com/AnvilCoder/Checkpo...
00:00:00 - Introduction
00:00:10 - Best Practices File
00:00:42 - Why Code Review Will Be in IntelliJ IDEA
00:01:32 - Structuring Files and Configuration in a Project
00:08:50 - Liquibase Review
00:12:16 - Two Options for Splitting a Project into Packages
00:14:45 - CarBrand Review
00:20:15 - Car Review
00:22:44 - NoAutoCarUpdateDB review
00:28:48 - Donation review
00:32:22 - Avatar review
00:42:24 - Checkpoint review
00:44:30 - Confirmation review
00:46:09 - Crossing review
00:50:45 - Service layer review
00:54:00 - Repository layer review
01:00:15 - Model review
01:08:34 - Utils review
01:13:15 - Tests review
01:19:24 - Summary