Reddit Reddit reviews The Information: A History, A Theory, A Flood

We found 33 Reddit comments about The Information: A History, A Theory, A Flood. Here are the top ones, ranked by their Reddit score.

Computers & Technology
Books
Computer Science
Information Theory
The Information: A History, A Theory, A Flood
Vintage Books
Check price on Amazon

33 Reddit comments about The Information: A History, A Theory, A Flood:

u/an-anarchist · 5 pointsr/cryptography

Yes and no. If you're asking these questions you'll probably be very interested in Claude Shannon's work. Take a read of his seminal information theory paper: http://cm.bell-labs.com/cm/ms/what/shannonday/shannon1948.pdf

For an easy read and a fun intro take a look at "The Information: A History, A Theory, A Flood":
https://www.amazon.com/Information-History-Theory-Flood/dp/1400096235/

u/OceansOnPluto · 5 pointsr/compsci

This is a little less scholarly and a little more geared towards history, but it's a fascinating read and one of the best books I've read in the last couple of years. It doesn't start with Claude Shannon, but rather with different ways that human beings have disseminated information to each other (talking drums, the telegram, etc), over the years. Definitely, after you're done with everything else, put this on your list, it's great.

Edit: Apparently I forgot the link. http://www.amazon.com/The-Information-History-Theory-Flood/dp/1400096235

u/vmsmith · 4 pointsr/statistics

A couple of these have been mentioned already:

  • Fooled by Randomness -- Nassim Nicholas Tabeb
  • The Black Swan -- Nassim Nicholas Taleb
  • The Drunkard's Walk
  • The Signal and the Noise (I'm almost finished reading it, and it's very good)

    [Note: Nassim Nicholas Taleb is an overbearing, insufferable egotist, but he says very interesting things, and I think his books are worth reading. I think he had an AMA on Reddit not too long ago.]

    Somewhat related, you might also consider The Information, by James Gleick. It pays to know something about the where and how the raw material of statistics.
u/CSMastermind · 4 pointsr/learnprogramming

I've posted this before but I'll repost it here:

Now in terms of the question that you ask in the title - this is what I recommend:

Job Interview Prep


  1. Cracking the Coding Interview: 189 Programming Questions and Solutions
  2. Programming Interviews Exposed: Coding Your Way Through the Interview
  3. Introduction to Algorithms
  4. The Algorithm Design Manual
  5. Effective Java
  6. Concurrent Programming in Java™: Design Principles and Pattern
  7. Modern Operating Systems
  8. Programming Pearls
  9. Discrete Mathematics for Computer Scientists

    Junior Software Engineer Reading List


    Read This First


  10. Pragmatic Thinking and Learning: Refactor Your Wetware

    Fundementals


  11. Code Complete: A Practical Handbook of Software Construction
  12. Software Estimation: Demystifying the Black Art
  13. Software Engineering: A Practitioner's Approach
  14. Refactoring: Improving the Design of Existing Code
  15. Coder to Developer: Tools and Strategies for Delivering Your Software
  16. Perfect Software: And Other Illusions about Testing
  17. Getting Real: The Smarter, Faster, Easier Way to Build a Successful Web Application

    Understanding Professional Software Environments


  18. Agile Software Development: The Cooperative Game
  19. Software Project Survival Guide
  20. The Best Software Writing I: Selected and Introduced by Joel Spolsky
  21. Debugging the Development Process: Practical Strategies for Staying Focused, Hitting Ship Dates, and Building Solid Teams
  22. Rapid Development: Taming Wild Software Schedules
  23. Peopleware: Productive Projects and Teams

    Mentality


  24. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency
  25. Against Method
  26. The Passionate Programmer: Creating a Remarkable Career in Software Development

    History


  27. The Mythical Man-Month: Essays on Software Engineering
  28. Computing Calamities: Lessons Learned from Products, Projects, and Companies That Failed
  29. The Deadline: A Novel About Project Management

    Mid Level Software Engineer Reading List


    Read This First


  30. Personal Development for Smart People: The Conscious Pursuit of Personal Growth

    Fundementals


  31. The Clean Coder: A Code of Conduct for Professional Programmers
  32. Clean Code: A Handbook of Agile Software Craftsmanship
  33. Solid Code
  34. Code Craft: The Practice of Writing Excellent Code
  35. Software Craftsmanship: The New Imperative
  36. Writing Solid Code

    Software Design


  37. Head First Design Patterns: A Brain-Friendly Guide
  38. Design Patterns: Elements of Reusable Object-Oriented Software
  39. Domain-Driven Design: Tackling Complexity in the Heart of Software
  40. Domain-Driven Design Distilled
  41. Design Patterns Explained: A New Perspective on Object-Oriented Design
  42. Design Patterns in C# - Even though this is specific to C# the pattern can be used in any OO language.
  43. Refactoring to Patterns

    Software Engineering Skill Sets


  44. Building Microservices: Designing Fine-Grained Systems
  45. Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools
  46. NoEstimates: How To Measure Project Progress Without Estimating
  47. Object-Oriented Software Construction
  48. The Art of Software Testing
  49. Release It!: Design and Deploy Production-Ready Software
  50. Working Effectively with Legacy Code
  51. Test Driven Development: By Example

    Databases


  52. Database System Concepts
  53. Database Management Systems
  54. Foundation for Object / Relational Databases: The Third Manifesto
  55. Refactoring Databases: Evolutionary Database Design
  56. Data Access Patterns: Database Interactions in Object-Oriented Applications

    User Experience


  57. Don't Make Me Think: A Common Sense Approach to Web Usability
  58. The Design of Everyday Things
  59. Programming Collective Intelligence: Building Smart Web 2.0 Applications
  60. User Interface Design for Programmers
  61. GUI Bloopers 2.0: Common User Interface Design Don'ts and Dos

    Mentality


  62. The Productive Programmer
  63. Extreme Programming Explained: Embrace Change
  64. Coders at Work: Reflections on the Craft of Programming
  65. Facts and Fallacies of Software Engineering

    History


  66. Dreaming in Code: Two Dozen Programmers, Three Years, 4,732 Bugs, and One Quest for Transcendent Software
  67. New Turning Omnibus: 66 Excursions in Computer Science
  68. Hacker's Delight
  69. The Alchemist
  70. Masterminds of Programming: Conversations with the Creators of Major Programming Languages
  71. The Information: A History, A Theory, A Flood

    Specialist Skills


    In spite of the fact that many of these won't apply to your specific job I still recommend reading them for the insight, they'll give you into programming language and technology design.

  72. Peter Norton's Assembly Language Book for the IBM PC
  73. Expert C Programming: Deep C Secrets
  74. Enough Rope to Shoot Yourself in the Foot: Rules for C and C++ Programming
  75. The C++ Programming Language
  76. Effective C++: 55 Specific Ways to Improve Your Programs and Designs
  77. More Effective C++: 35 New Ways to Improve Your Programs and Designs
  78. More Effective C#: 50 Specific Ways to Improve Your C#
  79. CLR via C#
  80. Mr. Bunny's Big Cup o' Java
  81. Thinking in Java
  82. JUnit in Action
  83. Functional Programming in Scala
  84. The Art of Prolog: Advanced Programming Techniques
  85. The Craft of Prolog
  86. Programming Perl: Unmatched Power for Text Processing and Scripting
  87. Dive into Python 3
  88. why's (poignant) guide to Ruby
u/grandzooby · 4 pointsr/compsci

Not exactly hardware focused, but I really enjoyed Gleick's "The Information, A History, A theory, A flood"

http://www.amazon.com/The-Information-History-Theory-Flood/dp/1400096235/

It does a great job of looking at computing in terms of information and its history. I loved the look at prominent figures like Babbage, Lovelace, Turing, etc.

u/rickg3 · 4 pointsr/FCJbookclub

I read books 4-6 of the Dresden Files. I blame Patrick Rothfuss for getting me started and duckie for keeping me going. Coupla assholes. After I finish the other 8 books, I have some nice, solid non-fiction lined up.

In no particular order, I'm going to read:

The Information by James Gleick

The Better Angels Of Our Nature by Steven Pinker

The Math Book by Clifford A. Pickover

The Know-It-All by A.J. Coastie Jacobs

And others. I'm gonna nerd out so hard that I'll regrow my virginity.

u/truancy-bot · 3 pointsr/math

In a way more general approach (and in my view), information is surprise. Anything else is just already known data presented in a certain way. I recommend The information by James Gleick for a detailed (and philosophical) analysis of this question.

u/scarletham · 3 pointsr/finance

Love stuff like this and this.

u/kaki024 · 3 pointsr/suggestmeabook

The Information: A History, A Theory, A Flood

https://www.amazon.com/dp/1400096235/ref=cm_sw_r_cp_apa_dZ3ozb100CF8D

u/walker6168 · 3 pointsr/AskHistorians

You should organize it by tech. Remember that numbers are tools. You're going to end up talking about what they were for more than the maths. Navigation, architecture, calendars, all of those would develop at different rates in a civilization and have math supporting it.

Just as two examples:

The beginning of basic numbers as a system would have been merchants and people accounting for debt/business transactions. There were a lot of mechanisms for doing this in early civilization via the temples, tribes, or governments. For details on that you should check out Debt: The First 5000 Years.

Computers are a different branch that deal with information transmission. James Gleick's outstanding book The Information: A History, A Theory, A Flood is a concise history of how we go from drum codes in the Congo to the Difference Engine to Turing's computer language.

u/Blindocide · 2 pointsr/DebateReligion

You should check out this book called The Information. it talks about information theory and how all material interactions are really just transferring information in the form of momentum and spin.

While I was hallucinating on 2C-E, after reading about schroedinger's cat, I had actually theorized that quantum interactions are, at a base level, information transfer. It was interesting to see that come up in a book way after I had thought of it.

/boast

u/[deleted] · 2 pointsr/worldnews

alan turing? If you don't know who he is, you need to.
start with The Information, a tremendous historical which he is featured in

u/ReinH · 2 pointsr/AskComputerScience

The Annotated Turing is fantastic! Also check out Turing's Cathedral for some insight into how his 1936 paper influenced computing into the next few decades and The Essential Turing to read Turing in his own words.

For a look at how Turing influenced information theory (and a fascinating general introduction to its history), check out The Information.

u/lisbonant · 2 pointsr/iamverysmart

For a historical and theoretical overview that doesn't get too technical but is still comprehensive and fun to read, I highly recommend The Information by James Gleick. If you dig Zero, I think you'd dig this.

u/colo90 · 2 pointsr/compsci

you must be referring to this book; you seem to have forgotten to include a link (or the name) to the book you're referring to

u/mightcommentsometime · 2 pointsr/math

My favorite relaxing math book was Chaos, Making a New Science by James Gleick

And The Information by James Gleick Was pretty good too.

u/EGKW · 1 pointr/Art

Thanks for the upvote. Have one from my side too. :-)
But that certainly isn't a semaphore station but indeed a windmill.
Semaphores and semaphore stations became somewhat popular starting from the end of the 18th century. The Ruisdael-painting dates from halfway the 17th century.
Furthermore (Chappe) semaphores had 2 arms, with 1 articulation each. The Ruisdael windmill clearly has 4 blades or sails.
If you want to learn some more about semaphores and sempahore stations there's an insightful chapter on that subject in James Gleick's book The Information.

u/mrdevlar · 1 pointr/StonerPhilosophy

Please read this:

The Information

It will resolve your question.

u/mike_bolt · 1 pointr/math
u/Navichandran · 1 pointr/ABCDesis

Yeah it was great. Alan turning was a genius.

One of my favorite books about information theory and entropy for all the nerds out there:

http://www.amazon.com/The-Information-History-Theory-Flood/dp/1400096235

u/Tamatebako · 1 pointr/suggestmeabook

I really enjoyed Richard Holmes' The Age of Wonder and also Chaos and The Information by James Gleick.

u/HasFiveVowels · 1 pointr/IAmA

To anyone interested in reading about this stuff, I'd very highly recommend "The Information" by James Gleick. It's probably my second favorite book and discusses information starting with African tribal villages sending messages with drums, going through to the telegraph, Shannon's creation of Information Theory, etc. A decent amount of the book is dedicated to Shannon and it's generally a great read.

u/SchurThing · 1 pointr/math

It's a good time for history of computer science books. We had Gleick's The Information last year, and George Dyson (Freeman's son) just published Turing's Cathedral.

u/steelypip · 1 pointr/DebateReligion

> What I don't see is why this distinction is particularly relevant to the point that information is a particular arrangement of matter and energy, as opposed to a third fundamental component of the universe...

You need matter and/or energy for information to be encoded, but it is something separate from any particular arrangement of matter and energy. The same information can be encoded in many different ways, and it is still the same information. Beethoven's 9th symphony is still Beethoven's 9th symphony whether it is encoded in pits burnt on a CD with a laser, an MP3 file stored on my hard drive, or a book of sheet music.

I recommend reading The Information: A History, A Theory, A Flood by James Gleick for an introduction to history of information theory as a science.

u/TroyHallewell · 1 pointr/todayilearned

I don't remember the details. But I do remember that this book goes into a bit of detail on how communication through the drums occurs.

https://www.amazon.com/Information-History-Theory-Flood/dp/1400096235

u/Aeelorty · 0 pointsr/freemasonry

But you did memorize something to do all those actions. Verbatim is not always necessary for proficiency but we should strive for that whenever ritual is concerned to avoid unintentional changes. The language we use does hint at all kinds of things. Changing a preposition could change meaning and disrupt a series of connections. If you want a more in depth rational for why I say memorization is important I suggest The Information by Gleick.