Think about it though. When people say they want to "code AI" what they typically mean is they want to play with prompts and waste electricity on garbage models, not actually write any of the underlying models that power AI.
this post was submitted on 23 Jul 2023
435 points (94.7% liked)
Programmer Humor
19463 readers
263 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
There's a huge gap between "playing with prompts" and "writing the underlying models" and they entire gap is all coding.
It really is big. From baby's first prompting on big corpo model learning how tokens work, to setting up your own environment to run models locally (Because hey, not everyone knows how to use git), to soft prompting, to training your own weights.
Nobody is realistically writing fundamental models unless they work with Google or whatever though.
I've even heard people try and call slightly complex bots "AI" and claim they can code them (or their friend totally can lol). It's infuriating and hilarious at the same time.
w++ is a programming language now 🤡
Not only that, but what I was aiming at was building applications that actually use the models. There are thousands upon thousands of internal tooling and applications built that take advantage of various models. They all require various levels of coding skill.
True! Interfacing is also a lot of work, but I think that starts straying away from AI to "How do we interact with it." And let's be real, plugging into OAI's or Anthropic's API is not that hard.
Does remind me of a very interesting implementation I saw once though. A VRChat bot powered by GPT 3.5 with TTS that used sentiment classification to display the appropriate emotion for the text generated. You could interact with it directly via talking to it. Very cool. Also very uncanny, truth be told.
All that is still in the realm of "fucking around" though.
I'm coming at it from the standpoint of implementing an AI model into a suite of applications. Which I have done. I have even trained a custom version of a model to fit our needs.
Plugging into an API is more or less trivial (as you said), but that's only a single aspect of an application. And that's assuming that you're using someone else's API and not running and implementing the model yourself.
You can make it as complicated as you want, of course.
Out of curiosity, what use-case did you find for it? I'm always interested to see how AI is actually applied in real settings.
We weren't using LLMs, but object detection models.
We were doing facial recognition, patron counting, firearm detection, etc.
Well yes, but also people can use TenserFlow and other AI tools without learning how to properly code. And they can also get the results they want. So be afraid of the question "do you really need to know how to code" anymore.
If you want to disabuse yourself of the notion that AI is close to replacing programmers for anything but the most mundane and trivial tasks, try to have GPT 4 generate a novel implementation of moderate complexity and watch it import mystery libraries that do exactly what you want the code to do, but that don't actually exist.
Yeah, you can do a lot without writing a single line of code. You can certainly interact with the models because others who can have already done the leg work. But someone still has to do it.
Same community reposts are back on Lemmy 😔
Hello ~~world~~ AI
And then they go to stackoverflow and ask why nothing works and he is getting just answers that he doesnt understand.
I'm still struggling with understanding for loops tbh. I kinda get them, but I can't "make my own" so I don't really understand them.
I've never had any schooling coding, just made some scripts with internet help when I switched to linux, and I have ADHD like fuck so I haven't really tried to understand them in months, but yeah if anyone knows of a good website to help learn for loops and how to create them (when to use what variables and brackets and shit, etc) I'm taking recomendations.
For i in website do $(tell me please);
(That can't be right lol, see, I need help!)
Don't let yourself down because you don't know the syntax off the top of your head.
Even after 15 years of programming, and studying computer science, I would have to look up how to write loops, conditions, variable assignments in bash / sh / batch.
Coming to python from a primarily java focus background wasn't any different. I knew what steps the program should do, but had to look up how to translate it into whatever language. And for further improvements what features the language has to express the things "in the style of the language"
Thanks, that encouragement is definitely helpful, it felt like I was struggling with something most programmers would consider should be mastered day 1, right after lunch because hello world is before lunch haha. Glad to know people still have to look it up even after a while sometimes.
For loops in scripting languages like bash should be a punishment. Try out something like python
Is your issue about just syntax?
for part in $text; do
echo "xX${part}Xx"
done
In bash, this loops over each word in a variable. If you want each line, you'll need to use a while read loop instead.
while read -r line; do
echo "xX${line}Xx"
done <<< "$text"
I think my issue may be more than just syntax, I really am inexperienced lol, all just learning as I go (unix philosophy and all lol, I kid).
The for loop I stole from the internet for use with ffmpeg is
for i in *$input; do ffmpeg -i "$i" "${i%.*}$output"; done
So I know what it does, it takes the input (read by the script earlier) filetype and changes it to the output filetype also read earlier for all of the files of $input type in the current directory, and I know how I got input and output as variables, and I know the ffmpeg -i foo -o bar command, but I get completely lost on "$i" "${i%.*}$output";. I don't really understand when to use what brackets or where I need semicolons and why, though I do understand that $ calls a variable and * is an operator to designate "all," I'm not entirely sure what this part of my script is doing (as this loop is the part I copied from stackexchange, and only half understood it "but it worked so fuck it" lol.)
The ${} syntax manipulates a variable. In this instance, I believe % removes a suffix. # is for a prefix. I can never remember which is which.
Semicolons just separate statements. You can replace them with a new line to get the same effect.
Thanks for the info, it definitely helped!
Also love it when people talk about “AI” without knowing what ML stands for and actually wanting to talk about ChatGPT. It’s hilarious.
I actually made this before chatgpt became so popular. At the time, the people I made this about wanted to use things like pytorch, tensorflow, and scikit.
Yes just wanted to apply your image to the current events and people “in AI”.
view more: next ›