Things to read or do next

• Functional data structures
• Soft typing paper
• 10 papers every programmer should read once
  • Papers could be fun, but it might be annoying to have to vote again every 2 sessions on what to do next. A list like this means we don't have to. If this list doesn't seem good we could find another list, or come up with one ourselves based on all the other papers listed.
• Functional programming pearls
• The New Turing Omnibus
• 10 Print Chr (205.5+Rnd(1)); : Goto 10
  • Less computationally intense than other suggestions as it's more about culture than computation. Might lend itself to a much more traditional book-club format.
• Hacker's Delight
• How to Design Programs
• Physically based rendering
• Think Complexity
• The simple nature of unix?
• Dependent Types Paper
• Eudyptula - linux kernel challenges
• Write software to make something move
• cryptopals: the matasano crypto challenges
• make something out of physical NAND gates
• The Haskell School of Music
• Types and Programming Languages
• Classic papers:
  • propositions as types?
  • paxos?
  • polymorphism in ML
  • RAFT
  • Kanren
• Beej's guide to network programming
• Declarative programming
  • through self-enumerating programs (In Quest of a Pangram)
  • actually build something
• Implement a protocol from its spec
• Little Prover
• Reasoned Schemer
• Architecture of open source applications
  • "In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program's major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think."
  • 24 chapters including e.g. Asterisk, bash, LLVM, sendmail, nginx, git.
  • Whole book available for free online in HTML under a Creative Commons license
• Introduction to Algorithms
• FPGA's