User Profile

Modern archaeology has drastically increased what we can learn from ancient ruins, and Newitz turns this lens on the history of how cities form, how they thrive, and how they die. The writing is engaging and accessible, flowing through what we know, how we know it, how certain we are about it, and the author's first-hand experiences with archaeologists at the actual sites.

The book has added a lot to my understanding of Pompeii and Angkor. Çatalhöyük is fascinatingly weird. And I'd really like to know more about Cahokia. (So would the people studying it!)

Satellites and Microscopes

There's a recurring theme of re-examining what we thought we knew, using either new technology or new perspective. Angkor is perhaps the best example: LIDAR surveys in the last 10-15 years have revealed the remains of building foundations and an irrigation network outside the walled temple complexes. It wasn't a medium-sized city crammed into those stone walls. It was a large city built around them. And mundane records of things like workers' shift assignments and rations, previously ignored by Western archaeologists, hint at changing political conditions in later years as the infrastructure failed.

Even Pompeii, with its ruins remarkably preserved under volcanic ash, and written records still available of not just administrative details but first-hand accounts of the eruption, benefits from taking a new look at records we already have: Cross-referencing census and death records for Pompeii and nearby towns reveals where survivors resettled.

There are no written records of Çatalhöyük (in modern Turkey) or Cahokia (in modern Illinois), only ruins and artifacts, but sometimes those artifacts have stored surprisingly detailed information: There are indications of a drought during the time the city was inhabited...and sure enough, residue from stews in cooking pots indicate that the people shifted to eating animals that need less water, and that the animals ate more drought-tolerant plants, around the same time.

Lifecycle of a City

Newitz makes a point of drawing parallels to modern cities. (Pompeii had fast food carts, ads, and sports riots!) Çatalhöyük is the most alien. It's one of the oldest cities known, and it seems people were still figuring out how to make one. All the buildings are basically cubes attached to each other, accessed through doors in the roof, and they all seem to have pulled multiple duty as bedrooms, kitchens, storage, etc. Kind of like a Minecraft house, if you could bury your dead relatives under your bed. (Sometimes they'd keep the skull in a wall niche, though!)

It's easy to think of these ancient cities as dead ends where civilizations failed. Unlike, say, Rome, where you can see a continuous line from the ancient city to the modern. But they weren't all cataclysms, and the people didn't just disappear. Cahokia seems to have been wound down when people were done with it, Çatalhöyük and Angkor slowly emptied out as people moved, and even Pompeii had survivors who resettled nearby.

They're not dead ends. They're stops along the way.

Cross-posted on my website.

A fun look at what it would be like to visit other planets or star systems, weaving together sci-fi scenarios, the science behind them, and the history of how those discoveries were made.

It starts with worlds we know the most about -- our moon and Mars, where we have plenty of direct measurements and photos from the surface -- and works its way out through asteroids, gas giants and their moons, and finally Pluto.

The second half of the book delves into more speculative situations. Types of places we know exist, like star clusters and nebulas and different types of stars. Plait links these to specific locations where possible. We know a system of planets exists around the red dwarf star TRAPPIST-1, for instance, and we have a rough idea of how big, how far, and how fast the planets are that we've spotted so far. From there he imagines: if one of the three planets in its habitable zone is enough like Earth to visit, what would it be like to experience a red sun, multiple planets with visible phases, and so forth.

There's some repetition, but I think part of that is trying to make each chapter stand on its own in case you want to jump ahead to, say, visiting a black hole. (You do not survive the encounter.) And while there's a lot that I knew already from following space exploration from a distance, there are newer discoveries I'd missed, things I'd known pieces of but never really connected, and a deep dive into topics I'd only skimmed the surface of before.

Also, there's an insert in the middle of the book with photos. I didn't notice it until I got there, so I'd been looking up NASA and ESA pictures of the specific comets and asteroids on my phone while reading!

Some fun facts: 1. Martian sunsets are blue! 2. The biggest asteroids are like miniature planets. The smallest are like bags of rocks without the bag. (Or a really unpleasant 3D ball pit.) 3. Saturn's rings are surprisingly thin. Like, millions of miles across but only 40 feet thick in places. 4. The Orion Nebula is a bubble at the near edge of an even bigger cloud of dust. We can only see it because it broke through on our side! 5. It's entirely possible for a planet to have a stable orbit around one star of a binary pair -- or both! Sunsets on a world like Tatooine would actually look like they do in the movies! 6. I'm still amazed at how much we managed to get from a single high-speed fly-by past Pluto.

Review cross-posted on my website.

Cool fact: Martian sunsets are blue.

On Earth, nitrogen scatters light randomly, with bluer colors scattering more than redder colors, so the ambient sky is blue, but when you're looking toward the sun at a shallow angle (like sunrise or sunset), most of the blue light is scattered into the next timezone and you see red and orange.

On Mars, tiny dust particles of iron oxides (rusty dust?) reflect yellow-orange light, making the daytime sky mostly a butterscotch color...but the particles that can stay aloft in the thin atmosphere are about the size of the wavelength of blue light, so they scatter blue light forward instead of randomly. So at the shallow angles of sunset and sunrise, the sky in the direction of the sun has more blue light than the yellows that are scattered in other directions.

Essentially the same process, but reversed because of the different content of the atmosphere!

It's been ages since I read any Discworld, but it seems appropriate that I came back to it with a time travel story involving a rebellion and barricades.

It's an interesting mix of serious and silly, sometimes both at once, often treating serious things as comedy and vice versa. The situation is messy, with good cops, bad cops, really bad cops, time ~cops~ monks, and a rebellion that today's Sam Vimes knows won't accomplish what it hopes to, even if it nominally succeeds. There's plenty of comedy in Vimes mentoring his younger self and trying to clean up the "old" watch just enough to keep history on track, how the ordinary citizens handle the rebellion [2], and yet it can still manage to punch you in the gut when you finally find out what the lilac sprigs in the present are all about.

Night Watch is in the middle of the City Watch series, but it takes enough time to establish the now that while I still spent a good chunk of the book wondering who I was supposed to already recognize, I had a good sense of what had changed over the years and the future Vimes is fighting to protect -- and how hard it is to put it aside so he can focus on the job in front of him.

Definitely recommended even if you haven't read the other Watch books!

Notes: 1. Even better: Next up in my DS9 rewatch is the episode with the Bell Riots. 2. In Les Mis, there's a point where one of the rebels remarks that they'll know they've lost the support of the people when old women are emptying chamber-pots on their heads. Since it's no longer to ask Terry Pratchett whether this was intentional, I'm going to assume it's a deep-cut reference to the book. hyperborea.org/les-mis/book/low-on-ammo/

Cross-posted on my website: hyperborea.org/reviews/books/nightwatch/

Still relevant despite recent advances in AI-generated imagery and text, because the new systems still work on the same principles as the ones that were around three years ago. They just have a lot more data and processing power. This also means they have the same limitations and blind spots. What was it trained on? How was it trained? (This is the most obvious way human bias can leak into an AI model.) How well is the goal specified? And of course, did the AI actually latch onto relevant details, or did it notice that all the training pictures labeled sheep had green fields and blue skies, and completely ignore the actual sheep?

These are things to keep in mind as we enter the landscape of generative AI tools like ChatGPT: You can train an LLM to write a book review, and it'll give you a great piece of text that reads like a book review -- but it's not going to have actually evaluated the book. For that, you'd have to train another AI to categorize books as good, bad, interesting, dull, and so on. But even that can only be as good as its training data. (I don't remember whether the classic phrase "garbage in, garbage out" is used anywhere in the book, but it still applies today!)

The author has a blog/newsletter, AI Weirdness www.aiweirdness.com/, where she pushes AI over the edge to sometimes hilarious results.

hyperborea.org/reviews/books/aiweirdness/

An excellent book that introduces the Rust programming language and why its features can make it a compelling systems level programming language. The book assumes the reader has some programming experience, so it doesn't go into basic programming concepts, but instead shows how Rust handles some standard programming tasks in a safer (and maybe better) way than other systems programming languages.

Rust's explicit use of ownership and keeping track of lifetimes enable the language to detect and alert programmers at compile time about issues with their code that would lead to memory access problems that are a major source of bugs in programs. Rust does not eliminate all bugs, but getting rid of memory access related bugs would be good for programming in general.

After covering those essential aspects of the language, the book then goes into some details about the ecosystem around Rust: separating code into libraries, producing test cases and documentation and adding dependencies and external libraries. The book also goes into some more advanced language features that can support object-oriented programming and use 'unsafe' features, where the programmer, instead of the language, has to take some responsibility to ensure the code is safe to use.

By the end of the book, you should have a good understanding of the language features and ready to produce code. The book also gives some pointers for those looking to use the more advance language features in their coding.