Here's a small example where things are pretty segregated:
https://github.com/illuminate/support/blob/master/Traits/Cap...
https://github.com/illuminate/queue/blob/master/Capsule/Mana...
And then the queue capsule manager is not to be confused with the database capsule manager:
https://github.com/laravel/framework/blob/master/src/Illumin...
When you're looking through a bunch of things similar to that, it can be a bit confusing to take it all in and remember what is what.
The other problem with anything built with Symfony components is that Symfony components never come with good defaults, they are a pain in the ass to instantiate manually, with huge object graphs because "decoupling". That's shouldn't be the case, one shouldn't have to create 15+ objects just to use a form factory for instance. Even Doctrine which is much more complicated than Symfony comes with acceptable defaults. Arrays/Maps of options passed as arguments of class constructors is a blatant demonstration that something is broken.
This leaves you digging through dozens of tiny files, some barely longer than the class definition itself, just to find even high level logic. I normally learn frameworks by simply reading the code, but I can't help but feel fatigued when having to try and find where a line of logic actually lives in Laravel. It is almost always a journey.