5 ms·

Sure, maybe you can use a shell script, but now the AI assistant can write it based on your verbal/text description, and then the assistant can also run it for

by nico 4y ago

Sure, maybe you can use a shell script, but now the AI assistant can write it based on your verbal/text description, and then the assistant can also run it for you after you’ve checked it. What your are saying is: “why use the washing machine, if I my clothes are even cleaner when I wash them myself - I also spend less detergent and less water”. You are free to keep doing your laundry by hand. But I bet most people prefer the washing machine.

xwdv 4y ago
Spare me the shitty analogies. We write shell scripts because it’s cheap, fast, and the behavior is very predictable. Like it or not, an AI’s behavior is a black box and can’t be “proven” to execute exactly the same every time for the scenarios you are targeting. A shell script will do exactly what it has been written to do every time, unless tampered with. And if changes need to be made, it can be done quickly without need for retraining, god knows how long that would take for an AI to learn something new. God help you if you need to maintain “versions” of your AI, trained for different things. Face it, AI are pointless and slow for certain classes of problems.
- com2kid 4y ago
  > A shell script will do exactly what it has been written to do every time, unless tampered with. Or unless some magic environment variable changes, or one of the runtime dependencies changes, or it is run on a different operating system, or permissions aren't setup right, or one of its tasks errors out. Shell scripts are digital duct tape, the vast majority of shell scripts do not come close to being reliable software. > god knows how long that would take for an AI to learn something new Did you watch OpenAI's demo yesterday? They pasted in new versions of API docs and GPT4 updated its output code. When GPT forgot a parameter, the presenter fed back the error message and GPT added the parameter to the request.
  - xwdv 4y ago
    AI proponents are missing the point. Anything you write to make an AI produce something is basically code. Docs are code. You don’t have to feed a developer code or docs, you can give them a high level idea and they’ll figure it out on their own if you want.
    - echelon 4y ago
      That code will eventually fall away. The big thing everyone in this single thread is missing is that AI is a metaheuristic. I wouldn't expect to use AI to run_script.py. That's easy. I'd expect it to look at the business signals and do the work of an intern. To look at metrics and adjust some parameters or notify some people. To quickly come up with and prototype novel ways to glue new things together. To solve brand new problems.
      - xwdv 4y ago
        To do the work of an intern an AI must go on Jira, read a ticket, then find the appropriate repositories where code needs to be modified, write tests for its modification, submit for code review, respond to feedback in code review, deploy its changes. It’s not there yet.
        echelon 4y ago
        This feels achievable in five years.
        suction 4y ago
        [dead]
        JohnFen 4y ago
        It always feels achievable in five years. People were saying exactly this 30 years ago. Sooner or later it may (or may not) be a true statement, but it's awfully hard for me to say that it's any different right now than it has been before.
- qup 4y ago
  > A shell script will do exactly what it has been written to do every time I wish I lived in that universe.
- njarboe 4y ago
  Correct. So are humans.
whatshisface 4y ago
I think you're fighting an uphill battle because of what you picked to defend here - shell scripts are very easy to write, and I have a hard time imagining a future where someone tells an LLM, "Write me a shell script that runs run_control.py with the speed argument set to one hundred." to get, "./run_control.py --speed 100"
- pstorm 4y ago
  That's a trivial example, sure. Think of saying "make this image more red, flip it vertically, then crop the bottom 25%, and finally output it with 80% compression as a jpg". That would take 15 minutes to figure out how to write that with imagick, or just have an LLM do it for you.
  - tough 4y ago
    I had to try, seems reasonable, haven't tested the code As an AI language model, I do not have direct access to image editing software, but I can provide you with a shell script that could achieve the described image manipulation using ImageMagick, assuming it is installed on your system. Here's an example shell script that you could use as a starting point: bash Copy code #!/bin/bash # Set the input image filename input_file="input.jpg" # Set the output image filename output_file="output.jpg" # Increase the redness of the image convert "$input_file" -modulate 100,150,100 -channel R -evaluate multiply 1.2 +channel temp1.jpg # Flip the image vertically convert temp1.jpg -flip temp2.jpg # Crop the bottom 25% of the image convert temp2.jpg -gravity South -chop 0x25% temp3.jpg # Compress the image to 80% convert temp3.jpg -quality 80 "$output_file" # Clean up temporary files rm temp*.jpg To use this script, save it to a file (e.g., "image_manipulation.sh"), make it executable (e.g., "chmod +x image_manipulation.sh"), and run it in the same directory as your input image. The output image will be saved in the same directory with the name "output.jpg". Please note that this is just an example script and may need to be modified depending on your specific image manipulation needs.
    - fulafel 4y ago
      This has lots of lossy encode/decode cycles that will accumulate artifacts. Good anecdote.

by nico 4y ago

xwdv 4y ago

Spare me the shitty analogies. We write shell scripts because it’s cheap, fast, and the behavior is very predictable. Like it or not, an AI’s behavior is a black box and can’t be “proven” to execute exactly the same every time for the scenarios you are targeting. A shell script will do exactly what it has been written to do every time, unless tampered with. And if changes need to be made, it can be done quickly without need for retraining, god knows how long that would take for an AI to learn something new. God help you if you need to maintain “versions” of your AI, trained for different things. Face it, AI are pointless and slow for certain classes of problems.

com2kid 4y ago
> A shell script will do exactly what it has been written to do every time, unless tampered with. Or unless some magic environment variable changes, or one of the runtime dependencies changes, or it is run on a different operating system, or permissions aren't setup right, or one of its tasks errors out. Shell scripts are digital duct tape, the vast majority of shell scripts do not come close to being reliable software. > god knows how long that would take for an AI to learn something new Did you watch OpenAI's demo yesterday? They pasted in new versions of API docs and GPT4 updated its output code. When GPT forgot a parameter, the presenter fed back the error message and GPT added the parameter to the request.
- xwdv 4y ago
  AI proponents are missing the point. Anything you write to make an AI produce something is basically code. Docs are code. You don’t have to feed a developer code or docs, you can give them a high level idea and they’ll figure it out on their own if you want.
  - echelon 4y ago
    That code will eventually fall away. The big thing everyone in this single thread is missing is that AI is a metaheuristic. I wouldn't expect to use AI to run_script.py. That's easy. I'd expect it to look at the business signals and do the work of an intern. To look at metrics and adjust some parameters or notify some people. To quickly come up with and prototype novel ways to glue new things together. To solve brand new problems.
    - xwdv 4y ago
      To do the work of an intern an AI must go on Jira, read a ticket, then find the appropriate repositories where code needs to be modified, write tests for its modification, submit for code review, respond to feedback in code review, deploy its changes. It’s not there yet.
      - echelon 4y ago
        This feels achievable in five years.
        suction 4y ago
        [dead]
        JohnFen 4y ago
        It always feels achievable in five years. People were saying exactly this 30 years ago. Sooner or later it may (or may not) be a true statement, but it's awfully hard for me to say that it's any different right now than it has been before.
qup 4y ago
> A shell script will do exactly what it has been written to do every time I wish I lived in that universe.
njarboe 4y ago
Correct. So are humans.

whatshisface 4y ago

I think you're fighting an uphill battle because of what you picked to defend here - shell scripts are very easy to write, and I have a hard time imagining a future where someone tells an LLM, "Write me a shell script that runs run_control.py with the speed argument set to one hundred." to get, "./run_control.py --speed 100"

pstorm 4y ago
That's a trivial example, sure. Think of saying "make this image more red, flip it vertically, then crop the bottom 25%, and finally output it with 80% compression as a jpg". That would take 15 minutes to figure out how to write that with imagick, or just have an LLM do it for you.
- tough 4y ago
  I had to try, seems reasonable, haven't tested the code As an AI language model, I do not have direct access to image editing software, but I can provide you with a shell script that could achieve the described image manipulation using ImageMagick, assuming it is installed on your system. Here's an example shell script that you could use as a starting point: bash Copy code #!/bin/bash # Set the input image filename input_file="input.jpg" # Set the output image filename output_file="output.jpg" # Increase the redness of the image convert "$input_file" -modulate 100,150,100 -channel R -evaluate multiply 1.2 +channel temp1.jpg # Flip the image vertically convert temp1.jpg -flip temp2.jpg # Crop the bottom 25% of the image convert temp2.jpg -gravity South -chop 0x25% temp3.jpg # Compress the image to 80% convert temp3.jpg -quality 80 "$output_file" # Clean up temporary files rm temp*.jpg To use this script, save it to a file (e.g., "image_manipulation.sh"), make it executable (e.g., "chmod +x image_manipulation.sh"), and run it in the same directory as your input image. The output image will be saved in the same directory with the name "output.jpg". Please note that this is just an example script and may need to be modified depending on your specific image manipulation needs.
  - fulafel 4y ago
    This has lots of lossy encode/decode cycles that will accumulate artifacts. Good anecdote.