3 ms·

Totally. All I want is an easier time navigating code; not getting lost in tabs and page scrolling, nested class structures and function references, interrupted

Totally. All I want is an easier time navigating code; not getting lost in tabs and page scrolling, nested class structures and function references, interrupted by context-switching text searches. It feels like I spend 75% of my brain capacity managing my short term memory. Your buddy mentor is a great formulation of the kind of AI aid I need. As for generating code, that's the least of my concerns. I'm actually happy when I get the opportunity to just hammer down some brain dead lines for a change.

ivanjermakov 4y ago
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
firatsarlar 4y ago
We're in same page. Me too constantly jump over code sections. I realized in many solutions to this, most effective could be meta thinking. Self awareness. I'm quick - like most of us - on editor, I'm quick at coding why ? It is kind of conditioning with time management. Quick thinking - assume - make us jumps, just like a battle with many fronts, keep your eye on that, then that . In reality, the code part we wrote in an one hour, probably done in one spark of brain act. Rest is coordination.

ivanjermakov 4y ago

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

firatsarlar 4y ago

We're in same page. Me too constantly jump over code sections. I realized in many solutions to this, most effective could be meta thinking. Self awareness. I'm quick - like most of us - on editor, I'm quick at coding why ? It is kind of conditioning with time management. Quick thinking - assume - make us jumps, just like a battle with many fronts, keep your eye on that, then that . In reality, the code part we wrote in an one hour, probably done in one spark of brain act. Rest is coordination.