I read it recently. I liked a few of the chapters especially how policy classes fix some issues with OO design. I do recommend asking an AI chatbot to summarize each chapter and say what the modern equivalent is since some of the idioms have improved. I think one whole section was obsoleted through the use of std::variant and std::visit.
My TI-85 story involves the fact that it only had 2D plotting (though I think newer models such as the TI-89 had 3D).
I had a 3D calculus class so I wrote a program in it to plot a 3D isometric mesh of a surface using the 2D rendering library. It was slow but got the job done. I used it to help pass a test or two.
I also experimented with drawing random surfaces and objects like a tire. They looked pretty cool for a calculator screen.
The math lab at the college had a cable which you could use to take data off or put it on so you could in theory have exchanged programs with others but this was before the internet so I didn't.
I still have mine and enjoy the sliding the cover off - a trip down memory lane.
Later I rewrote the program in QBasic on a PC for fun and it was lightning fast!
McPhee was recommended as someone whose writing "makes boring things interesting". I did enjoy The Curve of Binding Energy (nuclear science) and to some extent Coming out of the Country (Alaska). Both of those featured interesting vignettes and colorful characters which propelled along the narrative.
However, I then turned to his magnum opus on geology, Annals of the Former World. That was a long slog which, although I enjoyed moments of it, now I wonder if my time wouldn't have been better spent reading something more interesting.
I own every book McPhee published and have read each one at least twice. He is, without question, the finest writer of non-fiction I know. Annals, as you may know, was originally published as 4 separate volumes, each covering a particular US region. Assembling California is my absolute favorite McPhee work. I have a layman’s interest in geology and plate tectonics that I developed specifically because of this book.
I'm currently reading Assembling California (California resident, so I've seen all the things he discusses in the book, and wondered, like why is Half Dome so big and grey??). Like you I am rapidly developing a layman's interest in plate tectonics.
In every chapter there is a passage like this:
If you could pull up an acre of abyssal plain anywhere in the world -- lift into view a complete column of the ocean floor, from the accumulated sediments at the top to mantle rock at the base -- you would find the sheeted dikes about halfway down. In contrast to the rock columns you find all over the continents -- giddy with time gaps among lithologies of miscellaneous origin and age -- this totem assemblage from the oceans tells a generally consistent story. At its low end is peridotite, the rock of the mantle, tectonically altered in several ways on departure from the spreading center. Above the mantle rock lie the cooled remains of the great magma chamber that released flowing red rock into the spreading center. The chamber, in cooling, tends to form strata, as developing crystals settle within it like snow -- olivine, plagioclase, pyroxene snow -- but above these cumulate bands it becomes essentially a massive gabbro shading upward into plagiogranite as the magmatic juices chemically differentiate themselves in ways that relate to temperature. Just above the granites are the sheeted dikes of diabase, which keep filling the rift between the diverging plates. Above the sheeted dikes, where the fluid rock actually entered the sea, the suddenly chilled extrusions are piled high, like logs outside a sawmill. Because these extrusions have convex ends that bulge smoothly and resemble pillows, they are known in geology as pillow lavas. Above the pillows are the various sediments that have drifted downward through the deep sea -- umbers, ochres, cherts, chalk. Unlike the rest of the crust-and-mantle package, the sediments may hint at the surrounding world.
...
This guy basically writes in a way that transforms the book I am holding in front of my face, physically into a rock. Like some kind of magic trick. He clearly had so much fun writing this, it's amazing and very fun... if rocks tickle you even a little bit this book is worth reading.
Folks, in case it wasn't clear, I was complaining about people downvoting a critical opinion, I was not myself downvoting a critical opinion. I'm glad to see the trend on the original comment has reversed.
As I recall, Apollo 11 was off by 4 miles downrange, which was considered good but not precise. More work on the guidance / navigation system allowed for a precision landing in Apollo 12 (to touch down near a Surveyor probe).
If you want to read about this in fascinating detail, I highly recommend the book "Digital Apollo" by David A. Mindell.
David's book spends a lot of time dwelling on the tension between highly automated systems and the role of the human in them, and the HCI factors of the Apollo missions. They also recap each landing through that lens, including the major changes done to the Lunar Module UI (physical + software) and the landing script/programs for each mission and how things worked out in practice and how it was debriefed after. If you want the insight look at the decision to go for precision landing, how (and how well) it was achieved and how everyone involved felt about it, this is probably your best one-stop go-to.
And for anyone working in embedded UI, or around automation, etc. it's a wondeful mind-sharpener with many lessons in an inspiring applied context.
The Apollo user interface and computer were so state of the art that many of the problems and solutions remain quite similar today. I work in a similar area (cars, with ever-increasing amounts of automation, driver assistance and connectivity) and some of the debates and on-the-job exchanges and meeting notes cited in the book could be straight out of my day job 60 years later with only minute differences. Some of the "Lessons on Software Development"-type docs penned by Apollo engineers in the aftermath of the program (trade-offs of platform approaches and HW abstractions vs. optimization, how to get a handle on quality and testing, etc.) also still read absolutely modern to this day, almost with greater summarizing clarity than what decades of paradigms and jargon have slathered on top.
Thanks for that recommendation. Mendell's other book is not as exciting but they both are the pinnicle of historic technical writing, and yes, this is a sharepining tool for UI, enough to make it required reading.
Of course his interactions with the Apollo engineers is priceless. I worked for one such engineer, and the strain of perfection was great discipline.
So it was not uncovered by doge? and it is also not simply fraud? „Every year, agency reports posted online document billions in improper payments, which include fraud but also underpayments, duplicate payments, payments to ineligible recipients or for ineligible goods or services.“ (from the article you linked)
I'm wondering if any glass plates were recovered? I'm not sure they were all salvaged at the time, but I don't know how they would fare in the saltwater.
reply