User Profile

I read the book because Robert Seethaler was recommended to me, and in the book store this book had the most appealing blurb. Wien, Freud, the time just before the Nazis came to power in Austria.

Sometimes I wonder what I would do if I would have lived in the pre-Nazi time. Would I be a conformist? Would I close my eyes? Would I stand up? It is really hard to say, and the book did not bring me on a mental journey to figure that out. Or did I simply not get the main character? Why does he lie to his mother about Trnskie? Why does Franz suddenly decide to place Trnskie's trousers on the flagpole in the center of the city? This comes completely out of the blue, I mean, he does exactly what his "friend" Freud says to do. There is no explanation, no inner dialog (about this), nothing.

Also I was interested in learning something new about Sigmund Freud. Little of his work is well-received nowadays. But the book gives almost nothing on Freuds work, Seethaler uses him just as a prominent example. I think it is missleading to believe that Freud was in any way similar to the person Seethaler describes.

All in all, nothing new, nothing challenging, nothing out of the ordinary. It is well written though, has reoccurring elements like the doves or the associations with the rural life as a child. It has some wit. It is not monotone. But all that craft does not help since Seethaler has nothing to say.

To be frank, this book feels like a commissioned work: the Nazi theme, antisemitism, love, coming of age -- all nicely packaged and easy to read. An engineered smash hit.

From what I remember, Jonathan Frantzen is a fan of Alice Munro. If you don't have enough time to read a novel, read a story by Alice Munro -- that's his advice as I understood it. And that's what I did and enjoyed. A story reads in three hours, ideal for a slow afternoon in the park at the weekend.

There is probably a deep analysis, or even several, to each story. I'm not going to try to analyse the stories here in this review now. What I like, what I admire, is how Munro manages to take me out of the role of reader. The stories touch me.

I read "Dear Life" and "Too Much Happiness" in parallel. Some stories I have read several times: "Train", "Dimensions", "In Sight of the Lake" (inside?).

These books will certainly stay on my shelf and I will pull them out from time to time.

From what I remember, Jonathan Frantzen is a fan of Alice Munro. If you don't have enough time to read a novel, read a story by Alice Munro -- that's his advice as I understood it. And that's what I did and enjoyed. A story reads in three hours, ideal for a slow afternoon in the park at the weekend.

There is probably a deep analysis, or even several, to each story. I'm not going to try to analyse the stories here in this review now. What I like, what I admire, is how Munro manages to take me out of the role of reader. The stories touch me.

I read "Dear Life" and "Too Much Happiness" in parallel. Some stories I have read several times: "Train", "Dimensions", "In Sight of the Lake" (inside?).

These books will certainly stay on my shelf and I will pull them out from time to time.

The author explains entropy essentially with a dice-rolling experiment: Given N dice, e.g. all with the six on top, choose any dice (chance no. 1) and roll (chance no. 2). If the experiment is carried out often enough, the sum of the numbers on the dice approaches a value quite stably. It is very likely that the value 6N will not be reached again if N is sufficiently large.

It is clear from the experiment what is meant by (generally not directly measurable) specfic events (the numbers on the individual dice) and by (directly measurable) "dim" events (the sum of the numbers on the dice). I would have been interested to know whether the relationship between specific and measured events must always be linear.

The fact that 6N will most likely not be reached again is an illustration of the "arrow of time".
There are many more specific events that lead to a sum 3N or 4N than to 6N. This seems to me to be the main point of the book.

The author equates "entropy" with search cost, i.e. as a measure of missing information. I would have liked to see a proof of equivalence to the usual definition of entropy (sum of p log p over all p).

These are definitely important insights for me. I'm not sure if I needed to read this at this length to understand it. Why does this need to be discussed for 2, 4, 10, 100 and 10000 dices? And then again imagine that it's not numbers of dice but colours, smells, tastes or sounds?

I don't find the book entertainingly written. The examples from physics (Bose-Einstein configurations, Fermi-Dirac configurations) did not help me as a non-physicist. While reading, I had the idea that one could write a book "Entropy Mystified", where the many applications of this ingenious concept are presented.

I came across David Foster Wallace through his famous speech "This is Water". I then read some of his essays, about lobsters, about cruises, about severe depression and about how few good books there are on mathematics that can be understood by lay people.

The last essay in particular, "Rhetoric And The Math Melodrama", made me curious about how Wallace himself would write such a book on mathematics. And indeed, Everything and More is a unique non-fiction book.

I like the personal references: Wallace's niece is mentioned, the high school teacher gets a place of honour. I like how Wallace sketches the human side of the mathematicians (Kronecker, Cantor, Weierstrass, Dedekind et al) with one paragraph, I had an immediate image, and contrary to some biographies, I think these images are plausible.

I also like how he takes elements of textbooks on mathematics and plays with them. Abbreviations suddenly appear that have to be remembered, proofs, "interpolations". It may give a layman a sense of how mathematics is often written then and now.

The many footnotes and "IYI" ("if you're interested") insertions make the revision processes visible to me. Sometimes there is direct reference to notes from the editor, sometimes a footnote nullifies itself, "but in an interesting way". This brings Wallace closer to me, I am not only concerned with the text and its content, but also with Wallace, with the thoughts that (might) have led to the text.

From a mathematical-philosophical point of view, I find §1c particularly interesting, where two types of abstraction are presented: one where the concrete is inferred to the abstract ("horse", "forehead", "horn") and one where different abstractions are linked together ("unicorn"). I also find interesting, even if I don't yet know exactly what I will do with it, the criticism of the "Theory of Types" in §7f, according to which it is be a philosophically bad idea to derive definitions from paradoxes.

Mathematical induction, the epsilon delta technique and the diagonal proof are presented as techniques for dealing with the infinite. From my point of view, the compactification is missing, although the idea was touched upon. I would also have liked more on the axiom of choice. But I can understand that in a book where Cantor is the focus, it is only mentioned. (For those interested in mathematics: Eric Schechter in Handbook of Analysis and its Foundations really goes into this topic intensively from a practical point of view).

In short: a beautiful book that invites you to pay attention not only to the content but also to the form.

In March 2021 I passed the exam to become a "PRINCE2 Agile Practioner".
The training and the preparation for the exam were very helpful for me to reflect myself as a project manager in a consulting company.

In addition to the training, I had two textbooks at my disposal: the general PRINCE2 textbook ("Managing Successful Projects with PRINCE2") and "PRINCE2 Agile", which I will go into in more detail in a moment.

First, a brief introduction to PRINCE2. PRINCE2 is (as I understand it) a partially abstract system for describing project structures. I have the idea that some smart people have analysed a large portfolio of projects and have extracted and named recurring structures (principles, themes, processes) from it. For example, I found it interesting that it is not a good idea to bundle certain roles in the project in one person, e.g. project management and project assurance.

While PRINCE2 is quite abstract and formal, PRINCE2 Agile is an adaptation of PRINCE2 that works well for complex projects. Complex projects are projects where it is not clear in detail at the beginning how the project will proceed and are in contrast to complicated or simple projects.

Here, the author brings order to the different agile frameworks. On the one hand, there are agile practices (e.g. Scrum) and tools (Kanban). I use Scrum practices in particular more and more. The "time-boxing" of the sprints reduces stress because it protects against subsequent call-ins. Changes just have to wait until the next sprint. Stand-ups are helpful in a multi-project environment to remind people about the project.

But the word "agile" is not just about a working style. "Agile" needs framework conditions. The client has to be convinced of the iterative way of working and a flexible handling of quality and scope. And the team also needs to get to know agile practices and be willing to try them out. The book highlights this and gives valuable advice on how to achieve each.

For example, the "Agilometer" is presented, where agility is measured in six dimensions. Because according to the author -- whose name is Keith Richards, by the way -- "agile" is not to be understood categorically (yes/no), but metrically (more or less). In my opinion, the Agilometer is comparable to the newer Agile Fluency Model.

Although I found the book very helpful to learn about agile project management. However, I also needed the impetus provided by the exam, the incorrectly answered questions and the follow-up research. The book is not suitable to browse through in a quiet minute. It is heavily structured, with lots of lists and headings. It is not visually attractive. Therefore, it only gets 4 out of 5 points.

The next step in this topic for me is to apply the methodology to projects of all kinds, to take the time to apply the PRINCE2 terminology to what I am doing.