>>13285746Not a /sci/ but whatever.
This
https://htdp.org/ will teach you basics of programming. But won't get you employed. You need to look for jobs in your area and see what requirements they have. Choose a language, learn it, realize you don't know shit about algorithms and data structures, or even programming in general, then start reading CLRS, how do you read CLRS? By reading Basic mathematics and any book on proof writing, of course. To actually understand how shit works and why it works read CS:PP; read K&R before that. You need to know OOP, some parts of FP (knowledge of FP overall is helpful; there are numerous books on that, most of them are shit), also you need to learn some back/front end framework, preferably both. HTML and CSS you need to know by default, anybody knows that; you also need to know JavaScript (
https://javascript.info/). You need to know SQL if you're going to be a backend developer; No-SQL dbs are dead since the introduction of jsonb. In fact, you need to know database theory overall, at least the basics. Install GNU/Linux distribution, preferably Kubuntu (it has non-retarded interface simular to Windows, it's stable, and in general great as a daily driver for any not mentally ill person), and learn shell basics. In your spare time, read books about OS, networks and computer architecture by Andrew Tanenbaum. Do exercises in spare time from "Pro/g/ramming challenges v 4.0", google it. If any language/tech is interesting to you and you want to learn it, just type "best books about %shit%" in your search engine.
This is more of a mindmap than a roadmap.
Keep in mind that most of webdev monkeys don't even know/read the half of what I've listed. Most of the programmers are mongrels that doesn't deserve their wage; but businesses are desperate for developers since somebody has to do this shit. Maybe you can omit most of what I've listed and get hired anyway; maybe not. Depends on your luck.
Don't fall for hacker cult.
