[arbesman]

Glad you enjoyed the intro! In terms of the meat, there’s only so much that can be provided in an introduction, but I did step through the chapters at the end, explaining a bit of what is to come (though obviously not the meat itself: that’s found in the chapters themselves!).

But in terms of code itself, I do my best to convey how programming (and the world of code) feels. Admittedly, this is hard to do, but I talk about everything from different programming languages and what they are all about (and their vibes) to the unexpected power of global variables.

There is also a ton of computing history to be found in the book, which I think is vital for understanding the tech world (and building whatever comes next). We often see a certain amount of historical ignorance in tech, and that feels like a recipe for missing context, or unnecessary reinvention, or just plain not understanding the path dependence of this world. So I really try to explore that a lot.

[albumen]

"Show, don't tell". Why not post a bit of the meat, say chapters 2 and 3?

[arbesman]

I want to give people a sense of the breadth of the book, hence the introduction (and I had thought that it might be too confusing, jumping into the middle of things...). But reasonable point.

[Upvoter33]

rather, why not also post one "content" chapter? I think it will help sell the book better, fwiw