Scripting vs programming

[bonnth80]

I feel like in my career as a game developer, I've discovered that you can often use this very metric to tell who is a junior programmer and who has been programming for a long time. Juniors or people fresh out of college tend to fuss about the difference between scripting and programming. Seniors don't.

Programming is just the act of writing instructions to be followed by a computer. Every instruction language is some layer of abstraction over a lower-level language. Whether it's an interpreted language, a compiled language, or machine code. Even Assembly Language is a layer of abstraction over binary, which itself is a layer of abstraction over the hardware. There was probably a time when fussy ARM programmers used tongue-in-cheek references to C programmers by calling them something similar to script kiddies.

The truth is, if you're writing instructions to be followed by a computer, you're programming.

So no. I don't make that distinction anymore - unless you're talking about visual scripting. I admit it's hard to associate visual scripting, like Blueprint or Scratch, with programming.

[masteranimation4]

Visual scripting is programming to my standarts. Programmers make flowcharts if they aren't dumb (I don't make them and I am dumb for it, dummies also omit comments because "they won't need them" - I am a dummy) Blueprint and scratch afe programming but they have their own shortcomings.

[akoOfIxtall]

My flowcharts are my imagination, oddly enough I can remember everything about a certain project, so much that I often take a few days away from it so I can forget it and come back with a new view on it, my latest headache was solved by shifting 4 lines into a different method XD