Code navigations can be improved in a plenty of ways. I use JetBrains' IDEs daily, but most points can be applied to other IDEs/editors. Some things that helpe

Code navigations can be improved in a plenty of ways. I use JetBrains' IDEs daily, but most points can be applied to other IDEs/editors. Some things that helped me to become a lot more efficient: - Vim. Since you mostly edit code, not write it, it is reasonable to be in the editing mode by default, with a full keyboard of shortcuts you can use, not only ctrl/alt combinations. I use IdeaVim[1] plugin for Vim emulation. - Never use your mouse. Keyboard actions are faster and more consistent once you get used to it. IDEs and editors are highly customizable and should allow to bind almost any action. - Get rid of tabs, keep 1-3 active buffers in your vicinity. And then use ctrl+tab or ctrl+e to switch between them. - Learn tricks for code navigation: jump to definition/usage/implementation, search file/class/symbol. - Learn tricks for text navigation: pretty much any decent tutorial on Vim navigation will do. [1]: https://github.com/JetBrains/ideavim https://github.com/JetBrains/ideavim