Yeah probably, I don't use any IDE feature for ruby code. It's still a problem that all methods available in current scope are not immediately obvious, though. And if you try to inspect available methods on an object in a REPL console using `#methods`, there usually are hundredth of them, especially when using rails (although to be fair, it's not all due to inheritance, there are also a lot coming for mixins). I suppose ruby IDEs have the same problem.
When I write go code, I have a lot of static analysis tools, but I'm still glad it's easy for me to know what I can call without stopping for inspection.
Unfortunately jumping to definitions in Ruby is often hit-or-miss since the language is very dynamic and idiomatic Ruby code often uses a fair amount of metaprogramming.
Sounds like a shortcoming of your tools. I spend a lot of time in Visual Studio working on native C++ and even there I can ctrl-click on something and jump to the declaration or definition. I bet there's something even better for Ruby.