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.
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.
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 😔
Permanently Deleted
Of course AI does mean something - but it's a very broad term. It's a bit like saying you want to buy a vehicle. Could be a boat, car, truck or even a zeppelin.
I hope you like stats
Permanently Deleted
Hello
worldAIAnd 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" doneIn 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"; doneSo 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.)
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”.
