Comment by bakugo
5 hours ago
> But that's not programming because its a natural-language conversation?
Correct. Programming is writing code. You are not writing code, therefore you are not programming. I don't understand what's so complicated about this.
I'm literally making a program. Present-progressive of the verb to program. I feel like you're pearl-clutching on semantics. By my read, programming != writing code, but writing code is most definitely programming. Oxford defines 'to program' as both.
You're not making a program. You're managing the AI that is making a program. You're a manager, maybe a designer or architect too, but not a programmer.
These are well defined roles that existed well before AI. You don't get to redefine them just because you feel like you should get to be part of some imaginary "programmers' club" without doing the actual thing that defines the "programmer" role.
If you micromanage the mechanic, then yeah you might get production credits for fixing the car.
You could argue that I'm playing the manager, sure. I guess people who write software with nocode or visual data flow tools aren't programming in some form either? They aren't 'visual programming'? What about if I draw buttons and text boxes on a form in Visual Basic? I haven't hooked up the events yet, but that isn't programming?
Would you say that I am not programming if I make a synthesizer in Reaktor or Max? What about using blueprints in Unreal? Are those not programming?
This assertion that programming requires writing code is incorrect. I suspect the distinction cuts a little too close to home, which is why we are arguing semantics here.
It's sad to watch the mental gymnastics at play. I guess by asking my mechanic to service my car, I'm a mechanic too? I want it > it gets done > I am the doer. Ridiculous.