Where Wizards Stay Up Late book club questions

1. 1.

   Hafner and Lyon show that ARPANET's success depended heavily on informal trust networks among academics. Could the same project have been built inside a private company, or did the academic context matter?

2. 2.

   Licklider's memo imagining an 'Intergalactic Computer Network' circulated years before the technology existed. What does his example say about the role of speculative vision in technological development?

3. 3.

   The Request for Comments process was designed to make protocol design transparent and collegial. In practice, decisions were still shaped by who had institutional power. Does openness actually change who wins in technical debates?

4. 4.

   Email emerged as an unplanned use case and quickly dominated ARPANET traffic. Can you think of contemporary technologies where the actual use diverged sharply from the intended application?

5. 5.

   The book describes researchers working without any business model or user growth metric. What does that context — pure research funding, no commercial pressure — allow, and what does it prevent?

6. 6.

   ARPANET's early community was tiny, trust-based, and largely homogeneous. The modern internet is the opposite. What was lost in the transition, and was it lost inevitably?

7. 7.

   Packet switching was controversial and took years to be accepted. The skeptics weren't stupid — they had real arguments. What does the story of its adoption say about how radical technical ideas gain legitimacy?

8. 8.

   The book is careful to credit many contributors. Does reading it change any assumptions you had about who invented the internet?

9. 9.

   ARPANET was military-funded but academically operated. How did that hybrid create both freedoms and constraints that shaped what was built?

10. 10.

    By the end of the book, the network exists but the commercial internet is still years away. What decisions in the early ARPANET period made the commercial internet easier or harder to build?

11. 11.

    The book was published in 1996, before the internet became central to daily life. Reading it now, what feels prescient and what feels naive about how the early builders thought about what they were creating?

How to run the discussion

• Pick six to eight, not all of them. An hour of real discussion covers fewer questions than anyone expects, and racing the list is what makes a book club feel like homework.
• Open with what people noticed, not what they concluded. Asking for a verdict first hardens opinions before anyone has heard each other.
• Let the disagreement run. The questions below that split a room are the ones worth the time; the ones everyone answers the same way can be skipped.
• Ask the quiet person a specific question. A direct, narrow question is far easier to answer than an open invitation to contribute.