Been doing Ruby full-time for 3+ years, bunch of experience before that. there's heaps of good tooling for finding the method source and docs dynamica

Been doing Ruby full-time for 3+ years, bunch of experience before that. there's heaps of good tooling for finding the method source and docs dynamically I know, but this is a huge problem with a lot of code I see in the wild because this stuff is (ab)used so widely in Ruby-land. If I have to run code just to see where `Foo.bar` is defined, that makes things... about an order of magnitude harder to understand. I mean, that's really tough thing to do in anything but a trivial codebase. This is nearly 100% the fault of developers, not the language itself, but I would suspect that most Ruby developers spend a significant amount of time dealing with things like this because it's how the ecosystem rolls.