I think most experienced Ruby engs tend to think of code as existing within a runtime which is one global space with many nested (and parallel) execution states and rationalizing what's happening in static code means simulating that runtime in your head and navigating around it up, down and sideways.

This may seem like something all languages require but the way it works for me in Ruby is much different than when I am writing JS or Python. It's kind of hard to explain.