4 ms·

No, there's a very very long tail of tasks that are too niche for a proper tool to exist for but it would be annoying effort to figure out yourself. My most re

No, there's a very very long tail of tasks that are too niche for a proper tool to exist for but it would be annoying effort to figure out yourself. My most recent example of this: write a script to delete all git branches that point to HEAD. Go ahead see how long it takes you to figure out the command for that, because it took me under 60 seconds with AI.

hajile 2y ago
This is the learning to fish problem. If you understand git well, a solution isn't very hard (eg, rev-parse each branch and compare to the rev-parse of the current branch and deleting if they match). If you don't understand git well, you shouldn't be turning into a script-kiddy pasting in whatever the AI spits out and hoping that it works.
- NewsaHackO 2y ago
  Your method still requires a script though
- johnfn 2y ago
  You are using "script-kiddy" as an ad hominem rather than making an argument with proper justification. "script-kiddy" refers to website vandalism and cracking. That has nothing to do with using AI to learn what rev-parse does. Learning about `git rev-parse` through documentation and learning about `git rev-parse` through AI fundamentally have the same outcome at the end of the day: you have learned how to use `git rev-parse`.
  - skydhash 2y ago
    > Learning about `git rev-parse` through documentation and learning about `git rev-parse` through AI fundamentally have the same outcome at the end of the day: you have learned how to use `git rev-parse`. But with a non-zero chance of hallucination.
    - Jensson 2y ago
      If you learn many things that way the chance grows to 100%.
  - hajile 2y ago
    I’m using it as a pejorative (not an ad hominem) for people who blindly trust unknown code because they don’t have any real understanding. It’s a shortcut for a whole, well-known and obvious argument about the danger of playing with things being your understanding. http://www.catb.org/jargon/html/S/script-kiddies.html http://www.catb.org/jargon/html/S/script-kiddies.html If you are using AI to learn, understand, and verify what it spit out, by definition, you aren’t a script kiddy. My argument was about how you use AI rather than a commentary on if you should.
    - johnfn 2y ago
      It is an ad hominem. "you shouldn't be turning into a script-kiddy" is guilt by association, see Wikipedia[1] or ask AI[2]. If you think that learning from AI is dangerous you should articulate why you think that. I find it neither "well-known" or "obvious". [1]: https://en.wikipedia.org/wiki/Ad_hominem#Guilt_by_association https://en.wikipedia.org/wiki/Ad_hominem#Guilt_by_associatio... [2]: https://chatgpt.com/share/6817b741-8a80-800c-8d5d-1b315806ddf4 https://chatgpt.com/share/6817b741-8a80-800c-8d5d-1b315806dd...
- IshKebab 2y ago
  > eg, rev-parse each branch and compare to the rev-parse of the current branch and deleting if they match Yeah now go and do that in under 60 seconds. You seem to be a bit confused. I understand Git very well. But AI can simply do this much faster than I could.

hajile 2y ago

This is the learning to fish problem. If you understand git well, a solution isn't very hard (eg, rev-parse each branch and compare to the rev-parse of the current branch and deleting if they match). If you don't understand git well, you shouldn't be turning into a script-kiddy pasting in whatever the AI spits out and hoping that it works.

NewsaHackO 2y ago
Your method still requires a script though
johnfn 2y ago
You are using "script-kiddy" as an ad hominem rather than making an argument with proper justification. "script-kiddy" refers to website vandalism and cracking. That has nothing to do with using AI to learn what rev-parse does. Learning about `git rev-parse` through documentation and learning about `git rev-parse` through AI fundamentally have the same outcome at the end of the day: you have learned how to use `git rev-parse`.
- skydhash 2y ago
  > Learning about `git rev-parse` through documentation and learning about `git rev-parse` through AI fundamentally have the same outcome at the end of the day: you have learned how to use `git rev-parse`. But with a non-zero chance of hallucination.
  - Jensson 2y ago
    If you learn many things that way the chance grows to 100%.
- hajile 2y ago
  I’m using it as a pejorative (not an ad hominem) for people who blindly trust unknown code because they don’t have any real understanding. It’s a shortcut for a whole, well-known and obvious argument about the danger of playing with things being your understanding. http://www.catb.org/jargon/html/S/script-kiddies.html http://www.catb.org/jargon/html/S/script-kiddies.html If you are using AI to learn, understand, and verify what it spit out, by definition, you aren’t a script kiddy. My argument was about how you use AI rather than a commentary on if you should.
  - johnfn 2y ago
    It is an ad hominem. "you shouldn't be turning into a script-kiddy" is guilt by association, see Wikipedia[1] or ask AI[2]. If you think that learning from AI is dangerous you should articulate why you think that. I find it neither "well-known" or "obvious". [1]: https://en.wikipedia.org/wiki/Ad_hominem#Guilt_by_association https://en.wikipedia.org/wiki/Ad_hominem#Guilt_by_associatio... [2]: https://chatgpt.com/share/6817b741-8a80-800c-8d5d-1b315806ddf4 https://chatgpt.com/share/6817b741-8a80-800c-8d5d-1b315806dd...
IshKebab 2y ago
> eg, rev-parse each branch and compare to the rev-parse of the current branch and deleting if they match Yeah now go and do that in under 60 seconds. You seem to be a bit confused. I understand Git very well. But AI can simply do this much faster than I could.