Not GP, but I can add my two cents.

The trick is to avoid idle browsing of the code. Be intentional about what you need to do.

I use tools like grep/ripgrep to get a more focused of the code. Then with the line number, I can jump directly to where I need to be. Same with tools like linters and compilers.

In the same file, I often use search instead of line/character movement. You search for a symbols and you just cycle through their location.

I don't think it leads to a better code. But badly organized code will make this harder, so you tend to think about organization.