Skip to main content

Logicomix - An Interesting Read

My friend lent me the book 'Logicomix - An epic search for truth'. What follows below is my notes from reading the book.

We usually associate comics with lighter subjects, but this book has attempted to present a very serious subject - the doomed search for mathematical certainty, doomed because Goedel put an end to it. What makes the book more interesting is that the authors are also characters in the book, along with Russel and others.

This book presents the story of Russel's quest for mathematical certainty and also covers a surprising amount of information about logic, mathematics and philosophy.

The giants of late 19th and  20th century mathematics and philosophy like Henri Poincare, Gottlob Frege, Kurt Goedel, Dave Hilbert , Von Neumann and Ludwig Wittgenstein along with their works all figure in this book.

I should say that the attempt to present a serious subject through comics has also succeeded because the book is readable, makes the content stick and  i couldn't put it down. I completed it in a train journey, in 5 hours.

For e.g. the reason for Principia Mathematica is provided like this in Russel's words

1. Mathematics must be based on logic
2. Frege creates the right logic (based on sets)
3. I find paradox  (Russel's paradox)
4. Whitehead and I must fix it ( Principia Mathematica)

Russel strived worked hard on #4 above till Goedel proved that it was impossible.

The book says it in Goedel's words as  "There will always be unanswerable questions. What i have proved in essence, is that arithmetic, and thus also any system based on it, is of necessity, incomplete". 

The same written in serious language, at the end of the book is given below.

Goedel shocked the mathematical world by proving, in his famous paper "'On undecidable propositions in the Principia Mathematica and Related systems', that any consistent axiomatic system for arithmetic, in the form developed in the Principia, must of necessity be incomplete. More precisely, the first of the two incompleteness theorems establishes that in a logical axiomatic system rich enough to describe properties of the whole numbers and ordinary arithmetic operations, there will always be propositions that are grammatically correct by the rules of the system, and moreover, true, but cannot be proven within the system. The second incompleteness Theorem states that if such a system were to prove its own consistency it would be inconsistent".

The above shows how much simplified the language used in the book is.This book should be looked at as an introduction to a very serious subject, where it does a very good job, and not an in depth study of the subject.   Makes me wonder why school text books don't come out in this format.


Popular posts from this blog

Kano Model of Customer Satisfaction - Notes to Self

Note: What follows is the notes taken from my study of Kano's model of Customer Satisfaction. I came across this model when i wanted to know if there was a structured approach that would help me prioritize features for software product development. 

To evaluate a product or service, following parameters are very important

The value provided - this helps attract customersThe Quality offered - This earns customer respectProduct or Service innovation - This helps differentiate from competition
But these are not perceived directly, but indirectly through the product and it's features. Kano's model help to group product features into 3 categories ( 6 categories, but only 3 are important) and there by makes it feasible to deliver value at a promised quality while offering innovation. 

The 3 important feature categories are 
Basic featuresLinear featuresExciters or DelightersBasic features are that must be present in the product to be successful. They are also referred to as must have…

Knowns, Unknowns and Project Management...

This article is a draft of a paper i started to write in september 2007 and left it where you see it today.  The purpose is to to come out with a conceptual framework through which “the knowledge needed to successfully execute a project” can be viewed and gauged and presents a brief outline of the same. As always comments are most welcome...
Financial Resources, Domain, Technology, Communication, Cultural Differences, Organizational Structure, Organizational Culture and Power Play within an organization are some of the factors that have an ultimate bearing on the success of a project.
All projects come in shades of grey is a fact that has to be acknowledged. For example, when we start a project, very rarely do we know everything about Project Requirement, Scope and other factors that impact the project. There will be lot of ambiguity and this ambiguity has to be accepted and put to proper use.
But the problem is that people usually look at these factors in black and white. This may be ac…

Aggressive Schedules - Few thoughts...

During my early years in the software industry, i used to look at people who worked in projects with aggressive schedules, in awe. The people working in such projects talked about, long hours, working week ends and heroic endeavors in their projects. The people who worked in such projects were given more awards and rewards, compared to others. i thought that this was the way to be.

After working in projects with aggressive schedules, I realized that what I saw was only the silver lining and there was a big dark cloud behind this ( talk about what experience can do for you). The common thread that linked all the projects was that all of them exhibited one or more of the following.
Project ended up delayed by more than 100% Project got cancelled Project got de-scopedProject has a high cost of maintenance.  Having been burnt up by working in projects with “Aggressive Schedules’, (henceforth denoted as AS), I understand that projects with aggressive schedules cause more damage than what we …