E
Sehr amüsantes Buch. Ich war sehr fasziniert von den Details bei den Anspielungen. Besonders lustig ist es, wenn man die anderen Bücher des Autoren kennt, da er sehr oft (subtil) auf sie verweist. Gerade bei der Hörbuchvariante bekommen die Charaktere noch deutlich mehr Tiefe.
Many excerpts from Nietzsches books but not very effective reflection on them. I would rather read his original works wholly again.
The beginning of the book is aimed at people who are new to the field of UX overall. The next big portion is a collection of UX methods. I liked the part about evangelism - however, I wished it would discuss common challenges way more in depth.
That said, it's still 4 stars for me, as I am going to recommend this to UX designers fresh in the field, especially in markets with low UX maturity.
Etwas besser als der erste Band, trotzdem nicht so ganz zufriedenstellend. Das Ende bleibt nicht klar, das Buch scheint unvollständig. Schade eigentlich, denn es hat durchaus Potential.
This book does not show only the importance of science - it also teaches a lot. Never stop asking questions is I think the most significant lesson you can learn from this book.
A must-read for everyone.
The book is about a postman who finds out that he will die of brain cancer. The devil appears and suggests a deal: For each extra day to live, an item from earth has to disappear (the devil will pick it of course). The postman agrees and starts thinking each day about the impact of the disappearance of simple things such as telephones or clocks.
At first, the story reminded me of Faust - but only because of the deal with the devil. The story went on quite differently. The book made me reflect about the impact of the existence of items in our lives and the emotional attachments. I enjoyed it a lot.
Since I read the book in Japanese, here are my two cents from a learner's point of view. The story has simple language which fits the character well. This also makes it easy to understand even though you might not know all words. The Kanji used in the book are very common and repeated frequently so looking them up wasn't too bothersome even though it has almost no Furigana. I am around N3 and I could understand about 95% of the book (with lookups) - so it is a good challenge without causing frustration. I read the first half while listening to the audiobook. The voice actors talk in an engaging way but quite slowly so they can be understood well. They also differentiate well between different speakers by changing the voice and setting the mood with accompanying ambiance music. The audoo book and physical book matched so it is a good book for a read-along.
First, thanks to Kersi for getting me this book for Christmas.
I'd really like the story of this book, I also enjoyed the writing style of Ransom Riggs. I couldn't stop reading, I had to continue in order to find out more and more about the island and its inhabitants. The author knows how to bound readers onto his book, by never letting them know what happens next. Also, the story wasn't common, not usual at all.
The pictures underlined the story very well and helped me to understand the mystery beyond the story.
I can give this book the full rating, 5 stars.
Main message of the book: Buy and hold a low-cost index fund and don't mess around picking stocks - buy the haystack.
The methodology is simple yet effective. However, the book feels unnecessary bloated and repeats itself multiple times. If you look up a blogpost on the GTD method, you will get the same information and value just like reading the book.
The first book was way better... This one got better in the end but the first 300 pages were quite boring to read.
This book is incredible. When I started reading, I didn't know what'll happen or what to think about it. But as I went on reading, it got better and better and it came to the stage, when I couldn't stop reading. I got into the story of Will and Lou, her struggle to make him happy, to change his mind. So emotional writing, a good writing.
4/5 stars rating for this great book.
This is a very good book on the structure and processes of a Product organization that incorporated Agile not only on a delivery level but on an overall organizational level. My personal highlight was the section about roadmaps and why (not) to use them and rather focusing on outcome. I also appreciate that in contrary to many other books on the topic, it also has a few chapters on transformational topics to create a switch.
The main idea of this book is the SUCCESS principle (Simple, Unexpected, Concrete, Credible, Emotional). The whole book is only about that principle. It is interesting (and more of a marketing/pitch advice I feel) but it could have been explained with less texts. There are many examples which illustrate the principles but for me it felt a little repetitive.
Durchaus sehr gutes Werk, um die Grundlagen von Scrum zu verstehen. Einiges wird zwar öfter im Laufe des Buches wiederholt und wirkt daher redundant. Da aber dennoch sehr viele Prinzipien vorgestellt werden, tut dies dem kaum einen Abstrich.
There are many interesting concepts in this book though some of them are a little bit basic. So if you know generally about design principles you won't learn much new.
“The 48 Laws of Power” by Robert Greene left me feeling disgusted. I only read half of the rules and couldn't finish it. The book's writing style felt manipulative and its emphasis on strategies for gaining power through manipulation was deeply unsettling. Instead of offering positive and ethical guidance, it seemed to glorify deceit and manipulation as tools for success. Greene's approach, filled with examples of cunning and exploitation, made me uncomfortable and conflicted. While it presents historical insights, its glorification of these darker aspects of human behavior made it a challenging and distasteful read for me.
If you never heard any Software Engineering principles, the book might be a decent read. It explains principles like estimation, types of tests, project management etc.
However, it stays very basic and does not go much in depth.
It was only just as the title tells: Experiences of test automation but no helpful explanation of clear processes of the companies.