Order of learning low-level programming?

Question

assembler

Hello. Straight to the point. Apparently, I started learning low-level programming from the wrong place, so I ask you to correct the procedure. And I actually started by reading Tanenbaum about PC architecture. I read everything clearly, but I just can’t imagine analogies, so to speak, from the real world of practice. That is, as if I wrote on asme what he says. Therefore, isn't it better to first pee on asma, and then take on Tanenbaum? Or, on the contrary, is it better to finish reading it, and then take up practice in assembler?

Answer 1

I taught in this order:
- number systems: 2-digit, hexadecimal;
- representation of numbers in memory;
- processor device: registers, register size, their purpose, flags;
- organization of memory, addressing methods;
- actually the assembler itself.
But I understood 3-4 points only when I started writing in Asma, and before that - only vague ideas in my head. But after that, I had to leaf through books less.
PS. In general, to each his own, if it’s not clear to you from books, you can learn in parallel with asm.

Answer 2

I highly recommend this book https://www.ozon.ru/context/detail/id/125884/
The best for an introduction to computer devices and assembler.

Answer 3

without a real reference point, all knowledge will be transitive: "it flew into one ear and flew out into the other" so immediately look at some serious projects / topics.
in principle, knowledge of low-level programming and the hardware of a computer should be studied simultaneously.
assembler is the simplest language - there are only a few dozen commands in it :)
but the binding to the hardware is "iron", without it there is nothing in asme.
something is not clear in the codes, you start to study where it sticks out of the iron and vice versa.
then causal relationships between code and hardware begin to form in the skull, which makes you a low-level programmer :)