A fellow developer told me he worked the presented project along with the book and it greatly helped him to understand the content. I plan to do this myself one day.
I'm not afraid of object soup because first, the alternative is implementation soup, with methods that span several tens or hundreds of lines. There is little abstraction of high level concepts. Also it depends on the organization. I keep everything cohesive and organized in packages (or namespaces). With Maven, Gradle or most other build tools, you can even divide your application in Modules that don't know each other. If they need to communicate, they may use a common Message Bus, that is a separate module. Another advantage of this is that this makes it easier for you application to run distributed if desired.
I'm not afraid of object soup because first, the alternative is implementation soup, with methods that span several tens or hundreds of lines. There is little abstraction of high level concepts. Also it depends on the organization. I keep everything cohesive and organized in packages (or namespaces). With Maven, Gradle or most other build tools, you can even divide your application in Modules that don't know each other. If they need to communicate, they may use a common Message Bus, that is a separate module. Another advantage of this is that this makes it easier for you application to run distributed if desired.