Is the path of the programmer that I want to follow correctly built?

Question

Programming

Hello!
Is the path of the programmer that I want to follow correctly built? If there is an extra element - remove it, if not enough - add it.
Computer architecture - processor architecture - operating system design - machine code programming - assembly language programming - C - data structures - algorithms - software development.

Answer 1

Is the path of the programmer that I want to follow correctly built?

Depends on your ultimate goal and the expected time frame for reaching it.
This is practically one step, it can be combined with the "processor architecture" step.
It is useless to study the device of operating systems without practice, and for practice you need to know C and assembler.
It is better to start learning data structures and algorithms along with the language and before operating systems, because otherwise it will also be inconvenient.

Answer 2

Umm,.. well, I jumped something like this HTML -> PHP -> Linux so if you have an extra 10 years, then that's right))

Answer 3

When you step over the 3rd point - unsubscribe here.
I sincerely hope that you will overtake progress!
(at least ALREADY trying to state this - this is commendable)

Answer 4

learn immediately C or pluses

Answer 5

Too pre-planned, it will end up being completely different. What to plan? Take action!
Solve this issue step by step, i.e. set a goal of "software development" and immediately try to achieve it. Yeah, it doesn’t work out, so you learn exactly what is missing, in order for something to work out.
"Software development" is, frankly, a vague goal. What software? For example, if your software is in the field of finance, you will need to know economics, mathematics, and ..., but there are a lot of such areas and features.
And why do you need an assembler (a few programmers know it)? Now, if you need to know how it works, then find out.
Books are boring! Not enough good literature for beginners. Use the documentation as needed, i.e. read those parts that are interesting to you, you don’t need to read the documentation from cover to cover without putting anything into practice, 5 paragraphs are better but thoughtfully than all and just for the sake of theory. Theory is for you, for people your skills are more important. Not the fact that what you call "your theory" is really a theory.
Here you can read an interesting thin book that will tell you "how it is there further":

Alexander Nikitin, Dmitry Lyapin
Programmer's path
from $100 to $10,000 per month
2010 © Programming school
prog-school.ru
Didn't mean to criticize, but to save your time ;) Remember "Act!", reason in moderation.