Julio Biason
5 years ago
2 changed files with 60 additions and 0 deletions
@ -0,0 +1,31 @@
|
||||
+++ |
||||
title = "How To Survive A Horror Movie - Seth Grahame-Smith" |
||||
date = 2020-03-06 |
||||
|
||||
[taxonomies] |
||||
tags = ["books", "reviews", "movies", "horror", "seth grahame-smith"] |
||||
+++ |
||||
|
||||
[GoodReads Summary](https://www.goodreads.com/book/show/293217.How_to_Survive_a_Horror_Movie): |
||||
From ghosts, vampires, and zombies to serial killers, cannibalistic |
||||
hillbillies, and haunted Japanese videocassettes, How to Survive a Horror |
||||
Movie shows how to defeat every obstacle found in scary films. |
||||
|
||||
<!-- more --> |
||||
|
||||
{{ stars(stars=2) }} |
||||
|
||||
Honestly, I'm not sure who this book is targeted at. |
||||
|
||||
At first, I thought it would examine all the clichés on horror movies that |
||||
made the hero survive everything till the end. But the narration style |
||||
sometimes puts you as just someone living in the same world, sometimes it puts |
||||
you as the protagonist, sometimes you can engineer your way around every |
||||
problem, sometimes you have to force the screenwriter to do something (so you |
||||
don't actually _do_ whatever you need to do, you force someone else to make |
||||
you do something), sometimes you force the "movie" to move faster without the |
||||
screenwriter support... It is a huge hodgepodge of ways, and no consistency |
||||
between them. |
||||
|
||||
To be fair, I'm not a fan of horror movies (the book came from a Humble Bundle |
||||
pack) so I may appear a bit hard on the author, but still... |
@ -0,0 +1,29 @@
|
||||
+++ |
||||
title = " Microservices AntiPatterns and Pitfalls - Mark Richards" |
||||
date = 2020-03-08 |
||||
|
||||
[taxonomies] |
||||
tags = ["books", "reviews", "microservices", "antipatterns", "pitfalls", "mark richards"] |
||||
+++ |
||||
|
||||
[GoodReads Summary](https://www.goodreads.com/book/show/31291348-microservices-antipatterns-and-pitfalls): |
||||
Remember when service-oriented architecture (SOA) was all the rage? Companies |
||||
jumped in before fully understanding SOA’s advantages and disadvantages, and |
||||
struggled to make this complex architecture work. Today, we’re poised to |
||||
repeat this same experience with microservices—only this time we’re prepared. |
||||
With this concise ebook, author Mark Richards walks you through the ten most |
||||
common microservice anti-patterns and pitfalls, and provides solutions for |
||||
avoiding them. |
||||
|
||||
<!-- more --> |
||||
|
||||
{{ stars(stars=4) }} |
||||
|
||||
Not a book per se, but a paper about the tendencies that lead to microservices |
||||
to fail. If this was a book, I think I'd give it less stars, but since it is |
||||
just a short paper, it feels alright -- for a book, longer content and how to |
||||
implement the corrects would be nicer. |
||||
|
||||
In the end, for people starting with microservices, it is a good pointer for |
||||
"do not do that"; for people working with microservices for awhile, it's quite |
||||
a "I did that already" checklist. |
Loading…
Reference in new issue