@kirby @Hyperhidrosis
If you find yourself jumping to and fro the same blocks of code, check out bookmarks in Vim — probably the thing you need 🤷
But in general, you shouldn't be working on many things at the same time — keep focused, finish one function, make sure it works, then get back to the part that was supposed to call it, make your changes atomic — it will also make your commit log cleaner and easier to navigate.
@kirby @Hyperhidrosis
Don't get me wrong, I've also hated this approach: when you start working on a drawing, start with sketching out, then start working out details. Why the hell should I do it when I see that an eye would be here and I want to work on it right now.
But with time I grew to understand that it just doesn't work and that working on things in proper order helps you avoid lots of problems in the future and in the end helps keep the job as a whole done faster.
@kirby @Hyperhidrosis
I used to have lots of traits that today are attributed to zoomers: being able to have conversations with five different people with completely different contexts at the same time…
But I grew to realise that it's not a valuable skill at all — it just ruins your ability to concentrate and when you need it you just can't. Being able to concentrate for most type of tasks is a much more valuable skill.
I think that a lot of this has nothing to do with mice or text editors.
I'm pretty sure I'm just not experienced enough to be participating in debates like these, keep rethinking my arguments and then i realize there are a lot of cases I didnt think of and have not even experienced myself yet. Sorry
@kirby @Hyperhidrosis
It's fine — that's exactly what I do, sharing things I have figured out myself with time.
Of course you don't have to follow others' workflows to the letter and expect them to work for you, just try different approached and see for yourself what makes you more productive. There's no "righteous way" here — there are things that work for you (or at all) and things that don't.
