There is definitely a point in a framework with strong structure where it becomes easier to read the code than google the problem. But if you aren't working on a single codebase for a while you are definitely better off with google on your side.

Some frameworks are written in a way that makes reading the code a pain in the ass too, with generation, magic methods, annotations and other meta coding techniques that turn conventions into code. In those cases even if you have a really niche problem google may still be faster than delving into the dark depths of non-code.

I don't care how many years you've been programming, nobody git pulls a 10,000 class java codebase without nervously gulping.