>what does Sup Forums think the most job-prospective language is?
Depends on what type of job you want.
Realistically, there are two ways to learn to code. One of them is the easy way, the other is harder. Both get you a job, the hard gives you more choices about what that job is.
I define long term as being roughly:
>In two and a half years if you're doing this in some of your spare time, you could get an entry-level CS job, or you can do it in one year if you drop everything besides your job/school and just study.
The short term is about six months of semi-focused part time practice.
>For both the easy way and the hard way:
Language is irrelevant when new. You need to build some fundamentals that apply to all languages. In all cases you need to understand:
>Control flow, variables, arrays and strings
Basically, logic changing how you progress through a program (i.e If (a), do thing b), and the things that logic acts on. Learn by going CodeAcademy and working through any language for a few days.
>classes, constructors, and class functions; i.e, basic OOP
Modern programming thinks about things in terms of object oriented programming, which pretends your code can model an abstract-but-real thing. You do this with video games if you talk about "enemies" - bats, bugs, and monsters all are enemies. These gives tools to tackle big problems.
Find an intro course in your language on OpenCourseWare and work through their on-board and, if available, homework problems in this topic; I guarantee it will be covered.
>Data structures and algorithms; big O.
Doing things isn't enough. Modern programmers are expected to do and store things efficiently, and there are fast and slow ways to solve problems. The way you learn these ways is to practice. Find videos about this on OCW/youtube, and by reading Algo textbooks, working examples, and writing proofs of correctness. Cormen is good (though he wrote a brick). So is Kleinberg (though he'll kick your ass)
(1/2)