i wish the tech industry would just collapse already
-
-
I think this is why it just tires me out, instead of working with my code, I need to re-read and understand the new generated one.
-
@dragonfi @sabik @eniko i think it does have intent- the prompter’s intent; not any of its own. it seems to do best with problems that look kind of like translation. which is also its limitations; it can’t really do any work you didn’t already do. it can only transform it into a different “language”.
-
In addition, when I do it the hard way I get a good understanding of what is happening. With generated code, I can at most verify that it works, with a high chance that some details -- that I would have stumbled into otherwise -- would completely elude me.
-
-
@dragonfi @sabik @eniko i think it does have intent- the prompter’s intent; not any of its own. it seems to do best with problems that look kind of like translation. which is also its limitations; it can’t really do any work you didn’t already do. it can only transform it into a different “language”.
@dragonfi @sabik @eniko the whole think kind of reminds me of this bit of UI research done in the 1980s, that whenever i talk about it here i get a whole bunch of people really mad at me:
keyboard shortcuts don’t save any actual time. But they do make it feel like you’re saving time.
this really upsets the vim people
-
@dragonfi @sabik @eniko the whole think kind of reminds me of this bit of UI research done in the 1980s, that whenever i talk about it here i get a whole bunch of people really mad at me:
keyboard shortcuts don’t save any actual time. But they do make it feel like you’re saving time.
this really upsets the vim people
-
@dragonfi @sabik @eniko the whole think kind of reminds me of this bit of UI research done in the 1980s, that whenever i talk about it here i get a whole bunch of people really mad at me:
keyboard shortcuts don’t save any actual time. But they do make it feel like you’re saving time.
this really upsets the vim people
-
-
I think vim binds achieve two things for me:
- I don't get RSI from Emacs or navigating 4 submenus.
- Familiarity means I stay in the flow instead of wrangling the UI. I believe a good CLI would achieve the same.
Mouse is better at spatial and analog selection/manipulation. Keyboard is better at reproducibility and precise, well-defined actions.
I would never try to select an object in Blender via keyboard, but typing [E]xtrude 1.0, or text searching for Subdivide in the comman menu certainly beats using mouse only.
-
I think vim binds achieve two things for me:
- I don't get RSI from Emacs or navigating 4 submenus.
- Familiarity means I stay in the flow instead of wrangling the UI. I believe a good CLI would achieve the same.
Mouse is better at spatial and analog selection/manipulation. Keyboard is better at reproducibility and precise, well-defined actions.
I would never try to select an object in Blender via keyboard, but typing [E]xtrude 1.0, or text searching for Subdivide in the comman menu certainly beats using mouse only.
-
-
Not just faster, more precise and less fiddly. But that is 3D modeling.
I also agree that it doesn't worth the effort to learn keybinds you don't use a hundred times a day. (Look at pro Starcraft players, they have a valid reason to learn their most used keybinds to increase their Actions Per Minute.)
For code editing, I agree that there is no real difference between: (Shift-arrow to select line, Backspace) and "dd". I'm reading code way more than I write it.
-
R relay@relay.infosec.exchange shared this topic
I um... ehem. Yes it might. I use vim. 
