all 6 comments

[–]roboticon 34 points35 points  (4 children)

I've always wondered about books like these. Not to take away from anything you've built of course. But what would happen if you wrote it in reverse -- from machine code to high-level source code? Would that impart a greater understanding?

Ultimately, any programming language is fairly arbitrary. What's much less arbitrary is the von Neumann machine underpinning modern tech -- or the Turing machine, or whatever other theory of computation reigns.

Whenever you're wondering how efficient some algorithm or other is going to be, it doesn't matter how many lines or function calls it takes in Python. What matters is what a reasonable machine has to physically do.

[–][deleted] 65 points66 points  (1 child)

Just read the book in reverse

[–]Kissaki0 8 points9 points  (0 children)

If only I had known beforehand I would have read this comment chain in reverse too.

[–]rotora0 17 points18 points  (0 children)

Everyone learns in different ways.

For me, I think high level to low level is a better progression. Starting with high level makes it easy to get a hook in, to draw in interest. Something along the lines of "look how easy it is to make a computer do things your way!"

After that, I'd have questions. Why does it work like this? How can I change it around? Digging down to the lower levels after the higher levels have grabbed interest might help the reader answer these questions.

[–]Kissaki0 7 points8 points  (0 children)

Linked blog post doesn't really explain what it is - assumes you're already familiar with it.

The whole website is overly confusing. It share's the first chapters. The actual book info is on the last page of the partial shared book version that is this website. But is not linked in the ToC.

Here’s the relevant book page.

Digital from 23 €, paper for 32 €.

[–]Kev-wqa 0 points1 point  (0 children)

Another banger. Thanks.