It's sincere, in some places too vulnerable, even a bit senile. It's a window into a world I've never seen before.
The book is about the author trying to write a book that's at least as good as his previous books. And how he cannot do that, how ideas are killed in their infancy and so are hopes.
And there he is, in his own way, desperately open.
It was a slog, with a couple of good twists. The universe has had a lot of thought put into it, and it helps suspend the disbelief as a reader.
Yet, the writing and the plot makes it a challenging experience.
Suspense at its finest, the book is a stellar page-turner of which you want more and more. The characters, feel real and I found myself rooting for almost everyone in the book.
It's pure entertainment.
It's the Office Space and Karate Kid about DevOps put into a novel. Makes for a good airport read — it gets slightly technical and somewhere insightful.
The situation described in the book is very, very recognizable to anyone who ships software in a big company.
A personal story of how the King of Horror came to be. Features a lot of rejections, writing advice and the process of editing a story. It's a rewarding experience that gives a glimpse on the discipline, the craft and the failures of writing.
It also emphatically advocates against adverbs.
Zen and the Art of Motorcycle Maintenance sold as a rollercoaster of an adventure book featuring a split personality, soul-searching, and defining what things aren't.
Okay, in this one, the characters start drinking vodka on the third page.
It's also the most fun book I read this year.
It was predictable, stereotypical, impossible to believe and incredibly fun.
Like a good romantic comedy, there are no open questions, there are no unknowns and the stars in this world always align in such a way, that the most unlikely thing happens and advances the plot.
It's a cozy plot.
I admired it, it was simple, to the point and it felt humble... Until there was too much of it.
Yet, this was a hard read for me. The plot doesn't follow a traditional structure. It's sad and sincere. There's not a lot more to it than words.
I like the words in Breakfast of Champions. They are good words.
The book tells a story of how a literal ship, a submarine, could be figuratively turned around using some unusual management tactics. The author, a commander, exposes the steps the crew took to develop a clearer style of management. It worked for them.
It might work for us, too.
It was an eerie reading experience. A world in a world in a play in a book that references some historical figures but not others, to the point where it sounds so plausible. A myriad of open threads make a ball of mystery that never resolves and shouldn't. It's a difficult, perplexing, ambiguous and rewarding read.
This is a great overview of how the microservices can work for your product, team and organization. It's not going to teach you how to build a service tomorrow, nor will it show you the one true way of building software. On the contrary, it highlights the advantages and pitfalls of the microservices approach to building software. You, the reader, can decide whether it's for you.
It's the kind of technical book that you read without a computer. I like those books.
How did we get here?
The book explains what happened to us and why and argues how plagues, wars and famine have shaped our society. It features religions, including a new one.
A fascinating read.
If you can get past the tone, you are rewarded with an insightful read. We can't predict, so we might as well admit it and learn how to live. How? More exposure to the things that might help tremendeously and reduce the impact of things that might hurt.