What's even more ironic is that it's the most profound book about technical writing that I have yet found in my 12-year career.

It also inspired me to deep-dive into how the pages of my docs site relate to each other, which yielded some useful insights: https://technicalwriting.dev/data/intertwingularity.html

(Baker's book led me to Too Big To Know, which in turn led me to the concept of intertwingularity)

Hi. I wrote Too Big to Know, and your post intertwingled me with this thread, these books, and you.

(Note: I'm taking Google Alerts & Ego Salve as an ironic agent of Ted Nelson's concept of intertwingularity.)

Oh wow, cool! Thanks for writing the book and nice to meet you. Maybe it's time for Too Big To Know 2.0 given how GenAI is changing the data / information / knowledge / wisdom landscape so much? P.S. I am referencing your concept of networked knowledge in an upcoming conference presentation with my fellow technical writers.

I'm afraid I don't follow: what's unusual about the printed cover of the book, and why is the date of publication relevant to your assessment?

The damaged, scribbled collage of papers that forms the background image of the cover was a pretty odd design choice IMO: https://xmlpress.net/wp-content/uploads/covers/EPPO-Cover-Fr...

It's surely related to the central thesis of the book (quoted below) but I think there could have been a more appealing way to get that idea across

> What is needed today is the same rigor and discipline professional writers have long brought to making books, but not the same methodology. The book model does not work for the Web or for content consumed in the context of the Web.

It’s ugly, but ugly in a way that was more common 11 years ago.