I am starting this thread in response to a suggestion on my profile by
@Aspychata . I don't know what to learn or if I even need to. What is coding even about apart from building a computer from scratch or developing a website? It seems like a lot of job descriptions claim that knowing how to code is a plus and it doesn't always make sense to me that it would be. There are so many coding languages. How do you even know where to start? How many does a person need to know? Why does a person need to know them? I've tried some lessons before, but one of the apps I was using was discontinued and I dropped out of the other program. The app was teaching something called JavaScript. The other program also had JavaScript; but additionally, it had another course where I was learning how to read binary. Where would you even use any of this in real life? Within the program you just put the JavaScript code in and it draws a picture or in the case of the binary code it had me figuring out what was wrong in a line of code that caused an imaginary malfunction and I actually got that answer correct at the time, but what do you do with it when you are not inside a training app? Where do you even input it? Why do you need to write code to draw a picture when you can do the same without writing code? I don't understand tech hardly at all. Sometimes looking at this stuff makes me feel like I am not really smart after all.
I think that more important than learning a bunch of languages is to learn the logic, ones you learn the logic then picking the language becomes a matter of preferences, features and the so... after the logic, i'd would say the next skill is to understand systems get familiar with the flowchart symbols and be able to describe any system with such symbols... ones you understand the logic and are familiar with flowchart symbols you can write down any program in the world, before you even touch down on a language... now you can pick a language, considerations for the language can be personal preferences, hardware specifications, if you are running the program on top of an OS, what OS is that... security features, libraries... and so on...
"it had another course where I was learning how to read binary. Where would you even use any of this in real life?"
I would say it does not hurt to know something like this, if it gives you better understanding of the logic, but in reality if you are not designing circuits at component level, or your computer have modern specifications, this probably will no do much for you. This sounds like the kind of thing that was a must in the 80s. If you are not programming for a Comodore64 or for a wrist watch... you probably will never have practical use of this.
"Why do you need to write code to draw a picture when you can do the same without writing code?"
I am going to assume here, based on this 2 questions that you was interested on writing games... a drawing like a character in a game takes memory, no just to store but to render, and you will make that character move on the screen and also animate... look at how they program characters in old Nintendo games, like Mario... there are plenty of videos and websites explaining how this characters where programmed to be able to run the whole game on the hardware limitations of such consoles... today it is harder to hit this kind of limitations, but you still find them, like... what is the processor of an ATM machine, and why COBOL???