What can be read on the structure of the project organization?

Question

Java

Advise what should be read on the organization of the structure of projects, applications. Interested in the rules for the correct breakdown into packages, storage locations for configs, grouping tests. There are several desktop applications created for themselves (just for fun), there was a desire to bring the structure of their projects to generally accepted practices.

Answer 1

Clean Code
Clean Architecture
Custom Code
Refactoring
Design Patterns by O'Reilly

Answer 2

Of course, there are some generally accepted practices: to break everything into layers. which one depends on the project. how to mirror file - depends on the layers and frameworks / libraries.