books I read 2020
Once when I picked up a book from the local library, the librarian asked to tell her what I thought about the book when I would bring it back. Well, why not write a few lines about all the books I read so everybody could see what I thought about it? I'm often also happy to have friends recommend a certain book or tell me this and that is not really worth reading. I won't comment about the tons of books I have read so far, but about books I read from now on.
Of course, the book describes what happened in the summer of 1883, when the volcano Krakatoa ferociously blew apart and completely vanished. However, it is not only the event itself, the how and what, but also why this happened and how it affected not only the environment, but also the people, why and how it changed science, what effects this disaster potentially had on politics and religion... Some of the effects were not even local, but in other parts of the world. To understand some of the effects, it is important to understand the situation before this dramatic eruption and how this situation came to be, which is presented as well. Winchester goes into botanics, plate tectonics, trade, Dutch colonization, and more; all the time making the presented information approachable and interesting to read.
All in all, Ristić offers a very valuable guide for anybody who occasionally has to deal with SSL/TLS certificates. The guide is short enough to easily find what you need and even to read everything in a relatively short time. At the same time it is comprehensive enough to be useful in many situations.
A guide like this would have been helpful way back in the days when I designed a simple PKI for an enterprise. And I can recommend it to anybody who needs to create certificate or certificate sign requests on the command line without any special tools.
Even though the author claims to have lots of experience with designing systems around (transaction) logs at LinkedIn, he never gives any technical advice or hard facts on how to interconnect various systems, not even on how to structure the messages you are passing between the systems. Working more than 25 years in IT building various company-wide systems and services myself, I have read dozens of books published by O'Reilly and have come to appreciate this publisher for their high quality technical books. This book definitely does not even come close to the standard I have come to expect from O'Reilly. I ♥ Logs is more suited to a blog post or one of the cheap write-ups found with some other publishers.
Die äusserste schicht des buches ist die ich-form erzählung eines niederländischen kaffeehändlers. Herr Droogstoppel ist extrem von sich selber überzeugt und sehr geschwätzig und sein geschwätz hochgestochen und teils etwas nervig. Zum glück schreibt Droogstoppel das buch, welches er herausgeben möchte, nicht selber, sondern überlässt dies grösstenteils Stern, seinem Lehrling. Stern's stil ist sehr viel verständlicher, weniger verschnörkelt und nicht mehr nervig. Das buch, welches Droogstoppel mit hilfe von Stern schreibt, erzählt die geschichte des verwalters Max Havelaar, welcher in Java (Niederländisch-Indien, heute Indonesien) wirkt. Dies ist der eigentliche kern des buches und dreht sich um die art und weise, wie die Holländer während ihrer kolonialherrschaft in Java gewirtschaftet haben. Wie sie mit den lokalen leuten umgegangen sind. Wie sie die vor allem auf ihren eigenen kurzfristigen profit geschaut haben. Max Havelaar, selber einer dieser ausländischen verwalter, ist jedoch aus anderem holz geschnitzt; er interessiert sich für die lokale bevölkerung, kultur und gegebenheiten. Und er ist praktisch der einzige der versteht, dass langfristiger erfolg nur möglich ist, wenn diesen lokalen umständen rechnung getragen wird. Kurzfristiger grosser erfolg versus kleinerem aber anhaltendem erfolg.
Ich kann mir gut vorstellen, dass dieses buch zu der zeit, als es geschrieben wurde, als recht ketzerisch empfunden wurde, daher vielleicht auch der indirekte ansatz als geschichte in einer geschichte. Hat man sich erst mal an die etwas andere orthographie der damaligen zeit gewöhnt, so ist das buch recht einfach zu lesen, mit ausnahme der teile, in denen Droogstoppel zu worte kommt. Der kern der geschichte, also die erzählung über Max Havelaar, ist lesenswert; allerdings muss man sich erst durch ein paar 'Droogstoppel kapitel' kämpfen, bis diese wirklich beginnt.
Before long, Puller is more or less forced to team up with Veronica Knox, whose agenda and trustworthyness is not quite clear to him.
Even though it all looks like a rather straight forward escape from a place where escapes should not be possible, there is one troubling bit which does not sum up. With a lot of persistence, gradually a different perspective on things becomes plausible, but very difficult to argue, as this alternative perspective would mean that Robert Puller had been sitting in prison innocently for more than two years...
Unfortunately there are many jokes I did not really get, possibly due to some special meaning of some expressions (which not even my dictionary was willing to share with me), probably due to not being able to see some references to certain events or people (Neither am I British, nor is English my native language. I only have lived in the UK myself for a very short time many years ago and even though I am definitely no youngster any more, that was years after the last book of the three was written.) Nevertheless, many of these very short stories are entertaining. It is also refreshing to see something where people clearly can freely make fun of themselves and their peers, something which these days (I write this in 2020) is more and more drowned in the overwhelming movement of "political correctness".
John Puller, a top notch army investigator, again is up against forces much more resourceful than him and he is doing the investigation on his own, without any official backup by the army. After all, it is an investigation he does for himself and he is not supposed to be doing. It's all about the sudden disappearance of his mother. The case was never solved, but with new allegations from a dying woman and some new evidence, Puller is determined to find out what really happened that night, thirty years ago.
The investigation is not only difficult. And somebody seems to become nervous about what could be discovered because pretty soon anyone trying to look into the matter is being stonewalled by some forces that be.
The chapters in this book are short and plenty. It is told from two different perspectives, from John Puller's side and from Paul Rogers side and, as expected from the very beginning, somewhen the two trails of the story mix together and become one. The language is not too difficult and tension is kept high, lots of things happening. However, there are just too many events, coincidences and timings which are rather unlikely, too many characters which come too close to superhero. Baldacci's John Puller series is sometimes compared to Lee Child's Jack Reacher series. Yes, there definitely are similarities. Jack Reacher's adventures are the more credible ones.
What she does not know is about her special powers, about the Rajahs's plans for her, about how despicable humans can be and about love. All things she will learn before long.
The story is quite predictable and reading it without knowing who is the author, I could tell, from the love story, it was written by a woman. The ending is not a real ending, making it more desirable to get the next book in the series. All in all I think of this book more in terms of a love story with a little fantasy sprinkled in than the other way round.
Ku'Sox, the artificial daemon which can not be bested by any other daemon, understandably is not happy with the spell Rachel put on him. And he is of a mind to do something about it. Not only that, Ku'Sox's plan is much, much bigger. No longer will he have to endure any humiliation, every daemon and non-daemon will pay him homage and his race will become clean, superior. It's not only Rachel which is not so happy about such a plan, but also the daemons themselves. However, they are afraid of Ku'Sox, they dare not stand up against him. So it comes that Rachel, once fighting Daemons, is now trying to protect them. But Ku'Sox is stronger than any daemon, including her. Rachel, on the other hand, has more friends. Friends, though, can also be used against her...
Creating small microcontroller projects and accessing them in an "Internet of Things style" might look like a daunting task at first. It is not rocket science, but it definitely helps to have somebody showing you the ropes. And that's exactly what Charles Bell does with this book. For his introduction he chooses microcontroller boards running MicroPython. For following along, the Pyboard or a board from pycom (not only the WiPy, the LoPy4 etc. work equally well) are best suited, because all the samples are spelled out in detail for these boards. But Bell also discusses a number of other boards and gives enough details so that I feel I could master the samples with other boards too.
Charles Bell does a tremendously good job explaining all you need to know: the Internet of Things itself, MicroPython (and for that matter Python basics), programming basics, various microcontroller boards supporting MicroPython, hardware sensors, basics in electronics, ... There are always a number of samples, from simple gradually increasing to more involved. Links to hardware and the parts used are given, the hardware and protocols and programming techniques explained and the complexity is always kept in check. Working through the book and following along feels like you are taking a class with a helpful teacher. Things are explained in clear language, complexity is kept in check, the sequence of things in the book in a logical order, ...
I did have some experience in Python and internet protocols, but none at all in electronics or microcontroller board and I felt safe and well taken care of with this book. And I'm certain the same will be true for people knowing about electronics but not programming. And even if all the topics are new to you, you'll find this book extremely valuable.
The Unicorn Project is a business/developer book written in the style of an interesting story. It's in the perspective of Maxine, one of the best developers the company has. For some stupid reason, Maxine is transferred to a different section. Even though she is told to lay low for some time and later come back, she still wants to be useful in her exile. To be useful, she must be able to compile the code everybody is working on. But nobody seems to know the details needed to setup a working development environment. Maxine is not only skilled, but also persistent. And bit by bit she uncovers inadequacies after inadequacy and finds solutions for them or people with solutions.
Basically the book, by telling a story, teaches some important principles of modern software (and business) development. At times it seems like Maxine and her friends are inhumanly strong superheroes, but I can easily see how making the characters more humanly possible would require more characters and a more complicated setup in the story; the chosen setup therefor is in line with the main goal of the book: to teach some good principles.
If you have read and enjoyed "The Phoenix Project", you'll like this book as well. If you haven't read it, try either of the two and read the other if you liked the one you chose to read. Oh, and of course, try to apply the principles you learn from this book in your own environment; you might not be blessed with the same overly incredible success our superheros have, but hopefully you don't need to start out in such a hopeless environment either.