• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 14th, 2023

help-circle







  • The layout is what matters for vim and it’s derivatives. I might be wrong here, but if you really need to be able to use the same keybindings as you would on a English qwerty one, you could try remapping things to their addresses or whatever that’s called - basically the same key, physically, regardless of its layout mapping.

    That being said, it’s vim, you can remap the command to get back to normal mode from terminal mode to whatever key or key sequence you like most.

    Using mouse to scroll up and down your terminal window inside vim also gets you back to normal mode.

    And, well, quitting the shell of your terminal in vim works just fine - either via command or hitting Ctrl+d.








  • That’s the point - you have the expertise to make proper sense of whatever it outputs. The people pushing for “AI” the most want to rely on it without any necessary expertise or just minimal efforts, like feeding it some of your financial reports and have generate a 5-year strategy only to fail miserably and have no one to blame this time (will still blame anyone else but themselves btw).

    It’s not the most useless tool in the world by any means, but the mainstream talk is completely out of touch with reality on the matter, and so are mainstream actions (i.e. overrelying on it and putting way too much faith into it).



  • Pretty much this.

    It tends to depend on your branch, though, and in some fields, you really don’t need anything other than your code, because you’re not testing anything before it’s compiled anyway. For something like frontend development, on the other hand, having some extra screen space is a blessing, be it more monitors or just one bigger monitor, especially if you have the tools to easily manipulate the screen space, like automatic window tiling.

    To take the frontend example further, when you have something like i3/DWN/sway or any other tiling windows manager (that’s on Linux), you can easily set up more “desktops” (workspaces), divided into tiles like the browser window (to preview the changes), your editor (to make the raw changes), and the developer tools of the browser you’re currently testing things on. Not like it’s impossible to achieve the same with any other tool that lets you create virtual desktops, but the less time and brainpower you use on switching tabs/desktops/workplaces, which you achieve by always being able to access everything you need at a glance, just kinda helps you enter the flow state - you just dissolve into the process completely because you stare at everything you need all the time.

    The more you need to look at, the more you gain with these setups. The frontend example from above is a rather simple scenario, which is not too likely in this era, because you’re pretty much guaranteed to be using at least one framework, most likely with a live preview feature with real time output of the compiling results and errors. There’s no shortage of windows to open, all of which will be relevant and useful to your current task.

    Either that or put some non-work related crap on the side to switch to whenever you get mad because you don’t get the result you wanted to.