From 68346afc2e6af09cda59b6a6d981d876f9381988 Mon Sep 17 00:00:00 2001 From: Julio Biason Date: Fri, 20 Dec 2019 15:30:20 -0300 Subject: [PATCH] Removed the language tag from taxonomies --- content/announcements/juliobiason.net-3.0.md | 2 +- content/announcements/juliobiason.net-4.0.md | 2 +- .../things-i-learnt/add-then-remove/index.md | 2 +- .../books/things-i-learnt/always-vcs/index.md | 2 +- .../app-composition-stupid/index.md | 2 +- .../application-composition/index.md | 2 +- .../things-i-learnt/bad-code-defense/index.md | 2 +- .../books/things-i-learnt/blogging/index.md | 2 +- .../boolean-parameters/index.md | 2 +- .../books/things-i-learnt/cargo-cult/index.md | 2 +- content/books/things-i-learnt/coc/index.md | 2 +- .../things-i-learnt/code-formatters/index.md | 2 +- .../code-reviews-style/index.md | 2 +- .../books/things-i-learnt/code-style/index.md | 2 +- .../things-i-learnt/cognitive-cost/index.md | 2 +- .../command-line-options/index.md | 2 +- .../things-i-learnt/config-file/index.md | 2 +- .../books/things-i-learnt/crash-it/index.md | 2 +- .../books/things-i-learnt/data-flow/index.md | 2 +- .../books/things-i-learnt/data-types/index.md | 2 +- .../books/things-i-learnt/debuggers/index.md | 2 +- .../books/things-i-learnt/disclaimer/index.md | 2 +- .../things-i-learnt/document-and/index.md | 2 +- .../document-is-contract/index.md | 2 +- .../things-i-learnt/document-it/index.md | 2 +- .../books/things-i-learnt/fixable/index.md | 2 +- .../functional-programming/index.md | 2 +- .../things-i-learnt/future-trashing/index.md | 2 +- content/books/things-i-learnt/gerrit/index.md | 2 +- .../books/things-i-learnt/gherkin/index.md | 2 +- .../books/things-i-learnt/git-flow/index.md | 2 +- .../google-code-style/index.md | 2 +- .../books/things-i-learnt/handle-it/index.md | 2 +- .../things-i-learnt/hero-projects/index.md | 2 +- .../things-i-learnt/hero-syndrome/index.md | 2 +- .../integration-tests/index.md | 2 +- .../interface-changes/index.md | 2 +- content/books/things-i-learnt/intro/index.md | 2 +- .../languages-are-more/index.md | 2 +- .../things-i-learnt/languages-docs/index.md | 2 +- .../things-i-learnt/languages-tests/index.md | 2 +- .../learn-about-yourself/index.md | 2 +- .../books/things-i-learnt/libraries/index.md | 2 +- .../books/things-i-learnt/log-events/index.md | 2 +- .../magical-number-seven/index.md | 2 +- .../things-i-learnt/microaggressions/index.md | 2 +- .../books/things-i-learnt/monitoring/index.md | 2 +- .../books/things-i-learnt/not-done/index.md | 2 +- .../one-change-commit/index.md | 2 +- .../things-i-learnt/optimization/index.md | 2 +- .../things-i-learnt/outside-project/index.md | 2 +- .../things-i-learnt/own-your-shit/index.md | 2 +- .../things-i-learnt/paper-notes/index.md | 2 +- .../patterns-not-solutions/index.md | 2 +- .../things-i-learnt/people-care/index.md | 2 +- .../permanent-solution/index.md | 2 +- .../things-i-learnt/post-solution/index.md | 2 +- .../project-organization/index.md | 2 +- content/books/things-i-learnt/quit/index.md | 2 +- .../things-i-learnt/resist-easy/index.md | 2 +- .../things-i-learnt/responsible-code/index.md | 2 +- .../right-tool-agenda/index.md | 2 +- .../right-tool-obvious/index.md | 2 +- .../things-i-learnt/run-locally/index.md | 2 +- content/books/things-i-learnt/say-no/index.md | 2 +- .../things-i-learnt/small-world/index.md | 2 +- .../books/things-i-learnt/spec-first/index.md | 2 +- .../things-i-learnt/specialists/index.md | 2 +- .../things-i-learnt/start-stupid/index.md | 2 +- .../steps-as-comments/index.md | 2 +- .../things-i-learnt/stupid-bugs-list/index.md | 2 +- .../things-i-learnt/team-discussion/index.md | 2 +- .../books/things-i-learnt/tests-apis/index.md | 2 +- .../things-i-learnt/tests-dead-code/index.md | 2 +- .../tests-in-the-command-line/index.md | 2 +- .../things-i-dont-know/index.md | 2 +- .../books/things-i-learnt/throw-away/index.md | 2 +- .../things-i-learnt/time-to-stop/index.md | 2 +- content/books/things-i-learnt/time/index.md | 2 +- .../things-i-learnt/toxic-people/index.md | 2 +- .../things-i-learnt/transparent/index.md | 2 +- .../understand-shortcuts/index.md | 2 +- content/books/things-i-learnt/units/index.md | 2 +- .../things-i-learnt/use-structures/index.md | 2 +- .../things-i-learnt/use-timezones/index.md | 2 +- .../books/things-i-learnt/use-utf8/index.md | 2 +- content/books/things-i-learnt/users/index.md | 2 +- .../things-i-learnt/watch-reactions/index.md | 2 +- content/code/agile-vs-culture.md | 5 +- content/code/couchbase-example-and-rest.md | 3 +- content/code/dear-github-maintainers.md | 2 +- content/code/dont-diminish-types.md | 3 +- .../lets-not-call-it-unittests-anymore.md | 7 +- content/code/mocking-a-mock.md | 3 +- content/code/on-unittests-and-layers-2.md | 5 +- content/code/on-unittests-and-layers.md | 4 +- content/code/publishing-books-on-zola.md | 2 +- content/code/the-day-i-found-my-old-code.md | 3 +- .../code/when-i-used-pep8-to-fuck-up-code.md | 4 +- ...hy-mixing-tabs-and-spaces-is-a-big-deal.md | 4 +- ...ideo-games-you-must-play-before-you-die.md | 79 ++++++++++++++++--- content/reviews/books/12-years-a-slave.md | 43 ++++++++-- ...1-erros-classicos-da-gestao-de-projetos.md | 53 ++++++++++--- ...preguicoso-e-ter-resultados-em-sua-vida.md | 23 ++++-- ...-through-the-wilds-of-software-security.md | 24 ++++-- ...e-morte-a-partir-dos-elementos-quimicos.md | 43 ++++++++-- content/reviews/books/a-devils-chaplain.md | 2 +- ...plica-as-grandes-questoes-da-humanidade.md | 44 +++++++++-- content/reviews/books/a-garota-no-trem.md | 36 +++++++-- ...-historia-do-mundo-para-quem-tem-pressa.md | 40 ++++++++-- .../books/all-quiet-on-the-western-front.md | 46 ++++++++--- content/reviews/books/all-you-need-is-kill.md | 35 ++++++-- content/reviews/books/american-gods.md | 28 +++++-- .../an-illustrated-book-of-bad-arguments.md | 22 ++++-- content/reviews/books/angularjs.md | 17 +++- .../answers-to-questions-youve-never-asked.md | 4 +- .../books/antifragile-systems-and-teams.md | 21 +++-- ...sociacoes-ilicitas-e-ligacoes-perigosas.md | 47 +++++++++-- content/reviews/books/apache-kafka.md | 28 +++++-- content/reviews/books/argo.md | 46 +++++++++-- content/reviews/books/arrival.md | 45 +++++++++-- .../reviews/books/backbonejs-essentials.md | 29 +++++-- content/reviews/books/backbonejs-testing.md | 30 +++++-- content/reviews/books/being-there.md | 39 +++++++-- ...-programming-for-hackers-and-pentesters.md | 48 ++++++++--- content/reviews/books/brave-new-world.md | 50 +++++++++--- content/reviews/books/c-succinctly.md | 18 +++-- .../reviews/books/changing-planes-stories.md | 27 +++++-- content/reviews/books/chthon.md | 2 +- ...andbook-of-agile-software-craftsmanship.md | 60 ++++++++++---- .../books/clojure-for-machine-learning.md | 33 ++++++-- .../books/clojure-for-the-brave-and-true.md | 44 +++++++++-- .../coffeescript-application-development.md | 48 +++++++++-- .../books/como-a-musica-ficou-gratis.md | 57 ++++++++++--- .../como-convencer-alguem-em-90-segundos.md | 26 ++++-- ...iable-scalable-and-maintainable-systems.md | 48 +++++++++-- ...-ponto-criando-produtos-de-forma-enxuta.md | 44 +++++++++-- ...ango-design-patterns-and-best-practices.md | 31 ++++++-- ...le-went-to-war-and-started-a-revolution.md | 37 +++++++-- content/reviews/books/dossie-jung.md | 33 ++++++-- content/reviews/books/dragons-winter.md | 2 +- ...e-da-tesla-esta-moldando-o-nosso-futuro.md | 38 +++++++-- ...vealed-understanding-faces-and-feelings.md | 35 ++++++-- content/reviews/books/eon-the-way-1.md | 28 +++++-- .../reviews/books/films-from-the-future.md | 2 +- .../books/future-shock-future-shock-1.md | 30 +++++-- content/reviews/books/galaxy-in-flames.md | 2 +- ...the-life-and-science-of-richard-feynman.md | 42 +++++++--- ...rjs-javascript-framework-second-edition.md | 23 ++++-- ...one-the-art-of-stress-free-productivity.md | 46 ++++++++--- .../books/greek-mythology-explained.md | 2 +- ...icamente-incorreto-da-historia-do-mundo.md | 57 ++++++++++--- .../books/hadoop-in-practice-manning.md | 44 +++++++++-- .../books/handson-microservices-with-rust.md | 6 +- .../hap-and-leonard-blood-and-lemonade.md | 25 ++++-- ...uro-o-horizonte-do-brasil-no-seculo-xxi.md | 79 ++++++++++++++++--- content/reviews/books/horus-rising.md | 2 +- .../books/how-to-make-mistakes-in-python.md | 25 ++++-- content/reviews/books/i-am-legend.md | 25 ++++-- .../i-have-no-mouth-and-i-must-scream.md | 27 +++++-- ...ve-to-functional-programming-succinctly.md | 35 ++++++-- ...cience-faces-god-in-the-book-of-genesis.md | 33 ++++++-- ...tant-backbonejs-application-development.md | 18 +++-- ...-getting-more-productive-with-your-ipad.md | 34 ++++++-- .../javascript-testing-beginners-guide.md | 45 +++++++++-- ...fillment-beyond-the-starship-enterprise.md | 58 ++++++++++++-- ...n-to-program-in-lisp-one-game-at-a-time.md | 38 +++++++-- .../learn-you-a-haskell-for-great-good.md | 19 ++++- .../reviews/books/learning-ecmascript-6.md | 37 +++++++-- ...d-hybrid-mobile-applications-with-ionic.md | 29 ++++++- content/reviews/books/learning-java.md | 44 +++++++++-- .../books/less-web-development-essentials.md | 32 ++++++-- .../books/linux-shell-scripting-cookbook.md | 59 +++++++++++--- content/reviews/books/mastering-emacs.md | 2 +- ...ons-for-effective-javascript-web-design.md | 54 ++++++++++--- .../reviews/books/microservices-in-action.md | 4 +- .../reviews/books/modern-java-in-action.md | 3 +- ...opment-environment-with-vim8-and-neovim.md | 2 +- .../books/mujica-a-revolucao-tranquila.md | 40 ++++++++-- .../mussum-forevis-samba-me-e-trapalhoes.md | 40 ++++++++-- .../books/nginx-from-beginner-to-pro.md | 30 +++++-- .../books/night-of-the-living-trekkies.md | 27 +++++-- .../books/nos-bastidores-da-coca-cola.md | 40 ++++++++-- content/reviews/books/o-heroi-de-mil-faces.md | 63 +++++++++++---- content/reviews/books/o-principe.md | 31 ++++++-- ...ject-oriented-javascript-second-edition.md | 33 ++++++-- ...ternet-life-the-internet-and-everything.md | 21 +++-- .../books/old-mans-war-old-mans-war-1.md | 36 +++++++-- content/reviews/books/one-day-on-mars.md | 2 +- content/reviews/books/pense-como-um-freak.md | 32 ++++++-- ...es-extraidas-de-o-principe-de-maquiavel.md | 35 ++++++-- .../powers-annals-of-the-western-shore-3.md | 43 +++++++--- ...-history-without-the-fairy-tale-endings.md | 20 +++-- content/reviews/books/pro-vim.md | 2 +- ...ming-rust-fast-safe-systems-development.md | 38 +++++++-- .../python-3-object-oriented-programming.md | 36 +++++++-- ...undamentals-of-data-science-with-python.md | 35 ++++++-- ...eky-projects-for-the-curious-programmer.md | 27 +++++-- ...-e-um-bardo-contra-a-realidade-medieval.md | 24 ++++-- .../reactive-programming-with-javascript.md | 57 +++++++++---- content/reviews/books/ready-player-one.md | 35 ++++++-- content/reviews/books/redshirts.md | 30 +++++-- .../books/rin-tin-tin-a-vida-e-a-lenda.md | 67 ++++++++++++++-- content/reviews/books/rust-essentials.md | 40 +++++++--- ...-o-dobro-de-trabalho-na-metade-do-tempo.md | 42 ++++++++-- .../books/seven-languages-in-seven-weeks.md | 4 +- ...ive-reconnaissance-and-indirect-attacks.md | 36 +++++++-- content/reviews/books/soulminder.md | 2 +- .../storm-real-time-processing-cookbook.md | 28 +++++-- .../books/subterranean-scalzi-super-bundle.md | 50 ++++++++++-- ...ara-estudantes-porque-voce-pode-ir-alem.md | 29 +++++-- ...appreciation-of-the-worlds-finest-actor.md | 61 +++++++++++--- content/reviews/books/the-book-of-kells.md | 30 +++++-- content/reviews/books/the-book-of-skulls.md | 34 +++++--- .../reviews/books/the-complete-collection.md | 64 ++++++++++++--- content/reviews/books/the-cyberiad.md | 34 ++++++-- ...e-drawing-of-the-three-the-dark-tower-2.md | 23 ++++-- content/reviews/books/the-drift-wars.md | 36 +++++++-- content/reviews/books/the-emperors-soul.md | 22 ++++-- .../the-end-of-all-things-old-mans-war-6.md | 26 ++++-- content/reviews/books/the-forever-war.md | 43 ++++++++-- .../the-ghost-brigades-old-mans-war-2.md | 38 +++++++-- .../books/the-gunslinger-the-dark-tower-1.md | 25 ++++-- .../the-human-division-old-mans-war-5.md | 22 +++++- .../the-island-of-doctor-moreau-unabridged.md | 42 +++++++--- .../books/the-last-colony-old-mans-war-3.md | 47 ++++++++--- ...ittle-book-of-htmlcss-coding-guidelines.md | 26 ++++-- content/reviews/books/the-martian.md | 32 ++++++-- ...f-names-words-and-everything-in-between.md | 4 +- ...s-photographs-from-the-archives-of-nasa.md | 16 +++- ...rdinary-history-behind-ordinary-objects.md | 12 ++- .../books/the-swift-programming-language.md | 28 +++++-- .../books/the-waste-lands-the-dark-tower-3.md | 36 +++++++-- .../books/the-where-the-why-the-how.md | 5 +- content/reviews/books/the-wolfs-hour.md | 3 +- .../turing-e-o-computador-em-90-minutos.md | 31 ++++++-- .../reviews/books/typescript-succinctly.md | 26 ++++-- ...ild-bulletproof-web-apps-with-less-code.md | 51 +++++++++--- .../web-development-with-django-cookbook.md | 44 +++++++++-- ...s-inside-julian-assanges-war-on-secrecy.md | 41 +++++++--- ...isners-the-spirit-who-killed-the-spirit.md | 17 ++-- ...code-volume-i-understanding-the-machine.md | 42 ++++++++-- .../reviews/books/zoes-tale-old-mans-war-4.md | 33 ++++++-- content/thoughts/one-week-with-tiler/index.md | 2 +- .../pre-order-the-case-of-no-mans-sky.md | 3 +- .../thoughts/the-sad-life-of-walter-mitty.md | 3 +- .../things-i-learnt-the-hard-way-the-book.md | 2 +- .../thoughts/things-i-learnt-the-hard-way.md | 2 +- 248 files changed, 3773 insertions(+), 1045 deletions(-) diff --git a/content/announcements/juliobiason.net-3.0.md b/content/announcements/juliobiason.net-3.0.md index 01903d1..0b8103c 100644 --- a/content/announcements/juliobiason.net-3.0.md +++ b/content/announcements/juliobiason.net-3.0.md @@ -4,7 +4,7 @@ date = 2015-02-18 category = "announcements" [taxonomies] -tags = ["meta", "blog", "pelican", "en-au"] +tags = ["meta", "blog", "pelican"] +++ Short version: New blog URL, engine and layout. diff --git a/content/announcements/juliobiason.net-4.0.md b/content/announcements/juliobiason.net-4.0.md index 5f7dbb9..ef5dcf9 100644 --- a/content/announcements/juliobiason.net-4.0.md +++ b/content/announcements/juliobiason.net-4.0.md @@ -4,7 +4,7 @@ date = 2018-11-28 category = "announcements" [taxonomies] -tags = ["meta", "blog", "zola", "en-au"] +tags = ["meta", "blog", "zola"] +++ Short version: New new blog engine and layout. diff --git a/content/books/things-i-learnt/add-then-remove/index.md b/content/books/things-i-learnt/add-then-remove/index.md index bb088c7..4176040 100644 --- a/content/books/things-i-learnt/add-then-remove/index.md +++ b/content/books/things-i-learnt/add-then-remove/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - One Version To Add, One Version To Remov date = 2019-07-30 [taxonomies] -tags = ["en-au", "books", "things i learnt", "versions", "upgrades"] +tags = ["books", "things i learnt", "versions", "upgrades"] +++ A lot of things change during development. One day you need a field, another diff --git a/content/books/things-i-learnt/always-vcs/index.md b/content/books/things-i-learnt/always-vcs/index.md index 56c4fcf..0903fee 100644 --- a/content/books/things-i-learnt/always-vcs/index.md +++ b/content/books/things-i-learnt/always-vcs/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Always Use A Version Control System" date = 2019-07-08 [taxonomies] -tags = ["en-au", "books", "things i learnt", "source control", "vcs", "git"] +tags = ["books", "things i learnt", "source control", "vcs", "git"] +++ "This is my stupid application that I just want to learn something" is not diff --git a/content/books/things-i-learnt/app-composition-stupid/index.md b/content/books/things-i-learnt/app-composition-stupid/index.md index e7edb4e..b7f32dc 100644 --- a/content/books/things-i-learnt/app-composition-stupid/index.md +++ b/content/books/things-i-learnt/app-composition-stupid/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Even for Application Composition, Start date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "composition", "microservices"] +tags = ["books", "things i learnt", "composition", "microservices"] +++ Application composition may lead to microservices -- which is good -- but diff --git a/content/books/things-i-learnt/application-composition/index.md b/content/books/things-i-learnt/application-composition/index.md index 5741b65..7c2c9f7 100644 --- a/content/books/things-i-learnt/application-composition/index.md +++ b/content/books/things-i-learnt/application-composition/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Not Just Function Composition, But Appli date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "composition", "applications"] +tags = ["books", "things i learnt", "composition", "applications"] +++ When we were discussing [the magical number diff --git a/content/books/things-i-learnt/bad-code-defense/index.md b/content/books/things-i-learnt/bad-code-defense/index.md index a506f0f..c3879bc 100644 --- a/content/books/things-i-learnt/bad-code-defense/index.md +++ b/content/books/things-i-learnt/bad-code-defense/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Don't Defend Bad Code" date = 2019-07-31 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "bad code", "defend"] +tags = ["books", "things i learnt", "personal", "bad code", "defend"] +++ Bad code exists everywhere. You shouldn't defend it, even if it is your own diff --git a/content/books/things-i-learnt/blogging/index.md b/content/books/things-i-learnt/blogging/index.md index 4aa4516..ac6e683 100644 --- a/content/books/things-i-learnt/blogging/index.md +++ b/content/books/things-i-learnt/blogging/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Blogging About Your Stupid Solution Is S date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "blogging"] +tags = ["books", "things i learnt", "personal", "blogging"] +++ You may feel "I'm not start enough to talk about this" or "This must be so diff --git a/content/books/things-i-learnt/boolean-parameters/index.md b/content/books/things-i-learnt/boolean-parameters/index.md index 22517e3..ecefbaa 100644 --- a/content/books/things-i-learnt/boolean-parameters/index.md +++ b/content/books/things-i-learnt/boolean-parameters/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Don't Use Booleans As Parameters" date = 2019-06-23 [taxonomies] -tags = ["en-au", "books", "things i learnt", "booleans", "functions", "parameters"] +tags = ["books", "things i learnt", "booleans", "functions", "parameters"] +++ When you're designing a function, you may be tempted to add a flag (a diff --git a/content/books/things-i-learnt/cargo-cult/index.md b/content/books/things-i-learnt/cargo-cult/index.md index 85530a1..67069cb 100644 --- a/content/books/things-i-learnt/cargo-cult/index.md +++ b/content/books/things-i-learnt/cargo-cult/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Understand And Stay Away From Cargo Cult date = 2019-06-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "cargo cult"] +tags = ["books", "things i learnt", "cargo cult"] +++ "[Cargo cult](https://en.wikipedia.org/wiki/Cargo_cult)" is a type of cult diff --git a/content/books/things-i-learnt/coc/index.md b/content/books/things-i-learnt/coc/index.md index 8701a4b..1c7af0d 100644 --- a/content/books/things-i-learnt/coc/index.md +++ b/content/books/things-i-learnt/coc/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Code of Conduct Protect YOU, Not THEM" date = 2019-07-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "coc"] +tags = ["books", "things i learnt", "personal", "coc"] +++ When you're beginning with any language/library/framework, check their CoC; diff --git a/content/books/things-i-learnt/code-formatters/index.md b/content/books/things-i-learnt/code-formatters/index.md index 3796e84..6ddc523 100644 --- a/content/books/things-i-learnt/code-formatters/index.md +++ b/content/books/things-i-learnt/code-formatters/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Code Formatting Tools Are Ok, But No Sil date = 2019-07-16 [taxonomies] -tags = ["en-au", "books", "things i learnt", "code formatting", "code style"] +tags = ["books", "things i learnt", "code formatting", "code style"] +++ One thing a team may decide to fix the continuous flux of code style comments diff --git a/content/books/things-i-learnt/code-reviews-style/index.md b/content/books/things-i-learnt/code-reviews-style/index.md index a196917..70f735c 100644 --- a/content/books/things-i-learnt/code-reviews-style/index.md +++ b/content/books/things-i-learnt/code-reviews-style/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Code Reviews Are Not For Style" date = 2019-07-16 [taxonomies] -tags = ["en-au", "books", "things i learnt", "code reviews", "code style"] +tags = ["books", "things i learnt", "code reviews", "code style"] +++ When doing code reviews, do not focus on style; focus on design things that diff --git a/content/books/things-i-learnt/code-style/index.md b/content/books/things-i-learnt/code-style/index.md index 68124a8..b2dd0e0 100644 --- a/content/books/things-i-learnt/code-style/index.md +++ b/content/books/things-i-learnt/code-style/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Code Style: Follow It" date = 2019-07-16 [taxonomies] -tags = ["en-au", "books", "things i learnt", "code style"] +tags = ["books", "things i learnt", "code style"] +++ If your project have a defined code style, you must follow it. Sometimes it diff --git a/content/books/things-i-learnt/cognitive-cost/index.md b/content/books/things-i-learnt/cognitive-cost/index.md index bb86608..af3f731 100644 --- a/content/books/things-i-learnt/cognitive-cost/index.md +++ b/content/books/things-i-learnt/cognitive-cost/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Cognitive Cost Is The Readability Killer date = 2019-06-26 [taxonomies] -tags = ["en-au", "books", "things i learnt", "cognitive dissonance", "cognitive cost"] +tags = ["books", "things i learnt", "cognitive dissonance", "cognitive cost"] +++ "[Cognitive dissonance](https://en.wikipedia.org/wiki/Cognitive_dissonance)" diff --git a/content/books/things-i-learnt/command-line-options/index.md b/content/books/things-i-learnt/command-line-options/index.md index def1fb0..43a20ca 100644 --- a/content/books/things-i-learnt/command-line-options/index.md +++ b/content/books/things-i-learnt/command-line-options/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Command Line Options Are Weird, But Help date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "configuration", "command line options", "cli"] +tags = ["books", "things i learnt", "configuration", "command line options", "cli"] +++ In this day and age, when everything has a graphical interface, does it still diff --git a/content/books/things-i-learnt/config-file/index.md b/content/books/things-i-learnt/config-file/index.md index 4d51e11..0e70359 100644 --- a/content/books/things-i-learnt/config-file/index.md +++ b/content/books/things-i-learnt/config-file/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - The Config File Is Friend" date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "configuration", "config file"] +tags = ["books", "things i learnt", "configuration", "config file"] +++ Do not ignore the power of configuration files. diff --git a/content/books/things-i-learnt/crash-it/index.md b/content/books/things-i-learnt/crash-it/index.md index 055096b..bbff8fc 100644 --- a/content/books/things-i-learnt/crash-it/index.md +++ b/content/books/things-i-learnt/crash-it/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - It's Better To Let The Application Crash date = 2019-06-24 [taxonomies] -tags = ["en-au", "books", "things i learnt", "exceptions", "error handling"] +tags = ["books", "things i learnt", "exceptions", "error handling"] +++ Although that sounds weird, it's better to not add any error handling than diff --git a/content/books/things-i-learnt/data-flow/index.md b/content/books/things-i-learnt/data-flow/index.md index 6032428..c3e5711 100644 --- a/content/books/things-i-learnt/data-flow/index.md +++ b/content/books/things-i-learnt/data-flow/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Thinking Data Flow Beats Patterns" date = 2019-06-26 [taxonomies] -tags = ["en-au", "books", "things i learnt", "data flow", "design patterns"] +tags = ["books", "things i learnt", "data flow", "design patterns"] +++ When you're trying to find a solution to your problem, think on the way the diff --git a/content/books/things-i-learnt/data-types/index.md b/content/books/things-i-learnt/data-types/index.md index 22d86e6..2b629b4 100644 --- a/content/books/things-i-learnt/data-types/index.md +++ b/content/books/things-i-learnt/data-types/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Types Say What You Data Is" date = 2019-06-24 [taxonomies] -tags = ["en-au", "books", "things i learnt", "types"] +tags = ["books", "things i learnt", "types"] +++ Memory is just a sequence of bytes; bytes are just numbers from 0 to 255; what diff --git a/content/books/things-i-learnt/debuggers/index.md b/content/books/things-i-learnt/debuggers/index.md index 20b3343..1ea1474 100644 --- a/content/books/things-i-learnt/debuggers/index.md +++ b/content/books/things-i-learnt/debuggers/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Debuggers Are Overrated" date = 2019-07-08 [taxonomies] -tags = ["en-au", "books", "things i learnt", "debuggers", "debugging"] +tags = ["books", "things i learnt", "debuggers", "debugging"] +++ I heard a lot of people complaining that code editors are bad 'cause it's hard diff --git a/content/books/things-i-learnt/disclaimer/index.md b/content/books/things-i-learnt/disclaimer/index.md index 3bf6c40..3800200 100644 --- a/content/books/things-i-learnt/disclaimer/index.md +++ b/content/books/things-i-learnt/disclaimer/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Disclaimer" date = 2019-06-19 [taxonomies] -tags = ["en-au", "books", "things i learnt", "disclaimer"] +tags = ["books", "things i learnt", "disclaimer"] +++ There is one magical thing you need to know when reading this book: It's all diff --git a/content/books/things-i-learnt/document-and/index.md b/content/books/things-i-learnt/document-and/index.md index 8257644..fe4ba9e 100644 --- a/content/books/things-i-learnt/document-and/index.md +++ b/content/books/things-i-learnt/document-and/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - If A Function Description Includes An \" date = 2019-06-23 [taxonomies] -tags = ["en-au", "books", "things i learnt", "documentation", "single responsibility"] +tags = ["books", "things i learnt", "documentation", "single responsibility"] +++ Functions should do one thing and one thing only. I clear indication that diff --git a/content/books/things-i-learnt/document-is-contract/index.md b/content/books/things-i-learnt/document-is-contract/index.md index c408cda..5daa884 100644 --- a/content/books/things-i-learnt/document-is-contract/index.md +++ b/content/books/things-i-learnt/document-is-contract/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - The Function Documentation Is Its Contra date = 2019-06-21 [taxonomies] -tags = ["en-au", "books", "things i learnt", "documentation", "contracts"] +tags = ["books", "things i learnt", "documentation", "contracts"] +++ When you start the code by [writing the general flow as diff --git a/content/books/things-i-learnt/document-it/index.md b/content/books/things-i-learnt/document-it/index.md index 937a34a..4fc3bb7 100644 --- a/content/books/things-i-learnt/document-it/index.md +++ b/content/books/things-i-learnt/document-it/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Documentation Is a Love Letter To Your F date = 2019-06-21 [taxonomies] -tags = ["en-au", "books", "things i learnt", "documentation"] +tags = ["books", "things i learnt", "documentation"] +++ We all know writing the damn docs for functions and classes and modules is a diff --git a/content/books/things-i-learnt/fixable/index.md b/content/books/things-i-learnt/fixable/index.md index bb82fe1..8663c2c 100644 --- a/content/books/things-i-learnt/fixable/index.md +++ b/content/books/things-i-learnt/fixable/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Toxic/Aggressive People Are Not Fixable" date = 2019-07-23 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "microaggressions", "toxic people"] +tags = ["books", "things i learnt", "personal", "microaggressions", "toxic people"] +++ You may think "But I could go to those people and say 'Why are you being diff --git a/content/books/things-i-learnt/functional-programming/index.md b/content/books/things-i-learnt/functional-programming/index.md index 1b39597..a69afb5 100644 --- a/content/books/things-i-learnt/functional-programming/index.md +++ b/content/books/things-i-learnt/functional-programming/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Learn The Basics of Functional Programmi date = 2019-06-26 [taxonomies] -tags = ["en-au", "books", "things i learnt", "functional programming"] +tags = ["books", "things i learnt", "functional programming"] +++ At this point, you should at least have heard about how cool functional diff --git a/content/books/things-i-learnt/future-trashing/index.md b/content/books/things-i-learnt/future-trashing/index.md index 7487080..b8f96db 100644 --- a/content/books/things-i-learnt/future-trashing/index.md +++ b/content/books/things-i-learnt/future-trashing/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Future Thinking is Future Trashing" date = 2019-06-21 [taxonomies] -tags = ["en-au", "books", "things i learnt", "design", "solution"] +tags = ["books", "things i learnt", "design", "solution"] +++ When developers try to solve a problem, they sometimes try to find a way that diff --git a/content/books/things-i-learnt/gerrit/index.md b/content/books/things-i-learnt/gerrit/index.md index 3468149..7013502 100644 --- a/content/books/things-i-learnt/gerrit/index.md +++ b/content/books/things-i-learnt/gerrit/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Gerrit Is A Mistake" date = 2019-07-29 [taxonomies] -tags = ["en-au", "books", "things i learnt", "git", "gerrit", "source control"] +tags = ["books", "things i learnt", "git", "gerrit", "source control"] +++ I hate calling software "a mistake", but I can't find any other way to diff --git a/content/books/things-i-learnt/gherkin/index.md b/content/books/things-i-learnt/gherkin/index.md index 33fb01b..90f951f 100644 --- a/content/books/things-i-learnt/gherkin/index.md +++ b/content/books/things-i-learnt/gherkin/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Gherkin Is Your Friend to Understand Exp date = 2019-06-19 [taxonomies] -tags = ["en-au", "book", "things i learnt", "gherkin", "expectations"] +tags = ["book", "things i learnt", "gherkin", "expectations"] +++ Gherkin is file format for writing behaviour tests (BDD). But it can also give diff --git a/content/books/things-i-learnt/git-flow/index.md b/content/books/things-i-learnt/git-flow/index.md index a16001a..774ad6d 100644 --- a/content/books/things-i-learnt/git-flow/index.md +++ b/content/books/things-i-learnt/git-flow/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Git-Flow Is The Way To Go" date = 2019-07-30 [taxonomies] -tags = ["en-au", "books", "things i learnt", "git", "git flow", "source control"] +tags = ["books", "things i learnt", "git", "git flow", "source control"] +++ If [Gerrit is such a mistake](/books/thing-i-learnt/gerrit), what can you use diff --git a/content/books/things-i-learnt/google-code-style/index.md b/content/books/things-i-learnt/google-code-style/index.md index 5efeac4..a39ccb3 100644 --- a/content/books/things-i-learnt/google-code-style/index.md +++ b/content/books/things-i-learnt/google-code-style/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - ... Unless That Code Style Is The Google date = 2019-07-16 [taxonomies] -tags = ["en-au", "books", "things i learnt", "code style", "google code style"] +tags = ["books", "things i learnt", "code style", "google code style"] +++ Every freaking time Google comes with their own coding style, it's a garbage diff --git a/content/books/things-i-learnt/handle-it/index.md b/content/books/things-i-learnt/handle-it/index.md index d971a75..e93d8a1 100644 --- a/content/books/things-i-learnt/handle-it/index.md +++ b/content/books/things-i-learnt/handle-it/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - If You Know How To Handle It, Handle It" date = 2019-06-24 [taxonomies] -tags = ["en-au", "books", "things i learnt", "exceptions", "error handling"] +tags = ["books", "things i learnt", "exceptions", "error handling"] +++ If you know an error can occur, then you should handle it properly, instead of diff --git a/content/books/things-i-learnt/hero-projects/index.md b/content/books/things-i-learnt/hero-projects/index.md index 4f7bf44..7fb6942 100644 --- a/content/books/things-i-learnt/hero-projects/index.md +++ b/content/books/things-i-learnt/hero-projects/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - ... Unless That Code Style Is The Google date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "community", "teams", "hero project"] +tags = ["books", "things i learnt", "community", "teams", "hero project"] +++ An "hero project" is a project/spec change that you personally think will diff --git a/content/books/things-i-learnt/hero-syndrome/index.md b/content/books/things-i-learnt/hero-syndrome/index.md index d6908c3..45a0bd3 100644 --- a/content/books/things-i-learnt/hero-syndrome/index.md +++ b/content/books/things-i-learnt/hero-syndrome/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Don't Confuse Hero Project With Hero Syn date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "hero syndrome"] +tags = ["books", "things i learnt", "personal", "hero syndrome"] +++ Someone that suffers from Hero Syndrome will claim that things won't work diff --git a/content/books/things-i-learnt/integration-tests/index.md b/content/books/things-i-learnt/integration-tests/index.md index d6a2e62..212b3e3 100644 --- a/content/books/things-i-learnt/integration-tests/index.md +++ b/content/books/things-i-learnt/integration-tests/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Unit Tests Are Good, Integration Tests A date = 2019-06-19 [taxonomies] -tags = ["en-au", "book", "things i learnt", "unit tests", "integration tests"] +tags = ["book", "things i learnt", "unit tests", "integration tests"] +++ The view of the whole is greater than the sum of its parts. And that includes diff --git a/content/books/things-i-learnt/interface-changes/index.md b/content/books/things-i-learnt/interface-changes/index.md index de6ee26..b72a4a9 100644 --- a/content/books/things-i-learnt/interface-changes/index.md +++ b/content/books/things-i-learnt/interface-changes/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Beware of Interface Changes" date = 2019-06-23 [taxonomies] -tags = ["en-au", "books", "things i learnt", "interfaces", "apis"] +tags = ["books", "things i learnt", "interfaces", "apis"] +++ Interfaces and APIs is what you give away to others. If you keep changing them, diff --git a/content/books/things-i-learnt/intro/index.md b/content/books/things-i-learnt/intro/index.md index dbe03b6..d176b43 100644 --- a/content/books/things-i-learnt/intro/index.md +++ b/content/books/things-i-learnt/intro/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Intro" date = 2019-06-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "intro"] +tags = ["books", "things i learnt", "intro"] +++ "Things I Learnt The Hard Way (In 30 Years of Software Development)" started diff --git a/content/books/things-i-learnt/languages-are-more/index.md b/content/books/things-i-learnt/languages-are-more/index.md index ed09b2d..6a0aaa1 100644 --- a/content/books/things-i-learnt/languages-are-more/index.md +++ b/content/books/things-i-learnt/languages-are-more/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - A Language Is Much More Than A Language" date = 2019-06-24 [taxonomies] -tags = ["en-au", "books", "things i learnt", "languages", "community", "ecosystem"] +tags = ["books", "things i learnt", "languages", "community", "ecosystem"] +++ Picking a programming language is much more than just picking the words that diff --git a/content/books/things-i-learnt/languages-docs/index.md b/content/books/things-i-learnt/languages-docs/index.md index 17c39ff..5444871 100644 --- a/content/books/things-i-learnt/languages-docs/index.md +++ b/content/books/things-i-learnt/languages-docs/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Good Languages Come With Integrated Docu date = 2019-06-23 [taxonomies] -tags = ["en-au", "books", "things i learnt", "languages", "documentation"] +tags = ["books", "things i learnt", "languages", "documentation"] +++ If you're worried about learning some new programming language, you can bet diff --git a/content/books/things-i-learnt/languages-tests/index.md b/content/books/things-i-learnt/languages-tests/index.md index d1074a5..1239a1f 100644 --- a/content/books/things-i-learnt/languages-tests/index.md +++ b/content/books/things-i-learnt/languages-tests/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Good Languages Come With Tests" date = 2019-06-20 [taxonomies] -tags = ["en-au", "books", "things i learnt", "programming languages", "tests"] +tags = ["books", "things i learnt", "programming languages", "tests"] +++ You can be sure that if a language brings a testing framework -- even minimal diff --git a/content/books/things-i-learnt/learn-about-yourself/index.md b/content/books/things-i-learnt/learn-about-yourself/index.md index b5a1529..a8d74b9 100644 --- a/content/books/things-i-learnt/learn-about-yourself/index.md +++ b/content/books/things-i-learnt/learn-about-yourself/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - You'll Learn About Yourself The Hard Way date = 2019-07-19 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "burn out"] +tags = ["books", "things i learnt", "personal", "burn out"] +++ We get frustrated with code that doesn't compile. We get angry with customers diff --git a/content/books/things-i-learnt/libraries/index.md b/content/books/things-i-learnt/libraries/index.md index da487c4..4ad84d0 100644 --- a/content/books/things-i-learnt/libraries/index.md +++ b/content/books/things-i-learnt/libraries/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Create Libraries" date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "libraries", "project organization"] +tags = ["books", "things i learnt", "libraries", "project organization"] +++ One thing you must learn is how to break your project into smaller libraries, diff --git a/content/books/things-i-learnt/log-events/index.md b/content/books/things-i-learnt/log-events/index.md index 59b21cc..c0617d0 100644 --- a/content/books/things-i-learnt/log-events/index.md +++ b/content/books/things-i-learnt/log-events/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Logs Are For Events, Not User Interface" date = 2019-07-01 [taxonomies] -tags = ["en-au", "books", "things i learnt", "logs", "ui"] +tags = ["books", "things i learnt", "logs", "ui"] +++ Two things in one: First of all, when using logging, use it to log events, not diff --git a/content/books/things-i-learnt/magical-number-seven/index.md b/content/books/things-i-learnt/magical-number-seven/index.md index 3b18493..1733b94 100644 --- a/content/books/things-i-learnt/magical-number-seven/index.md +++ b/content/books/things-i-learnt/magical-number-seven/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - The Magical Number Seven, Plus Or Minus date = 2019-06-26 [taxonomies] -tags = ["en-au", "books", "things i learnt", "complexity"] +tags = ["books", "things i learnt", "complexity"] +++ "[The magical number](https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two)" diff --git a/content/books/things-i-learnt/microaggressions/index.md b/content/books/things-i-learnt/microaggressions/index.md index 32b6cab..ff04025 100644 --- a/content/books/things-i-learnt/microaggressions/index.md +++ b/content/books/things-i-learnt/microaggressions/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Beware of Microaggressions" date = 2019-07-23 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "microaggressions"] +tags = ["books", "things i learnt", "personal", "microaggressions"] +++ Microaggressions are defined as "brief, everyday exchanges that send diff --git a/content/books/things-i-learnt/monitoring/index.md b/content/books/things-i-learnt/monitoring/index.md index e33ef92..5133bf1 100644 --- a/content/books/things-i-learnt/monitoring/index.md +++ b/content/books/things-i-learnt/monitoring/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Logs Are For Events, Not User Interface" date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "monitoring"] +tags = ["books", "things i learnt", "monitoring"] +++ On a previous life, to understand how a system behaved, I added a ton of diff --git a/content/books/things-i-learnt/not-done/index.md b/content/books/things-i-learnt/not-done/index.md index ec53d13..238a5a1 100644 --- a/content/books/things-i-learnt/not-done/index.md +++ b/content/books/things-i-learnt/not-done/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Don't Tell It's Done When It's Not" date = 2019-07-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "responsibility"] +tags = ["books", "things i learnt", "personal", "responsibility"] +++ You are tired of running the same thing over and over again. You kinda diff --git a/content/books/things-i-learnt/one-change-commit/index.md b/content/books/things-i-learnt/one-change-commit/index.md index 41f6fdb..a406fa0 100644 --- a/content/books/things-i-learnt/one-change-commit/index.md +++ b/content/books/things-i-learnt/one-change-commit/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - One Commit Per Change" date = 2019-07-09 [taxonomies] -tags = ["en-au", "books", "things i learnt", "source control", "commits"] +tags = ["books", "things i learnt", "source control", "commits"] +++ When working with source control tools, keep one change per commit. Avoid diff --git a/content/books/things-i-learnt/optimization/index.md b/content/books/things-i-learnt/optimization/index.md index 576bb28..57b0866 100644 --- a/content/books/things-i-learnt/optimization/index.md +++ b/content/books/things-i-learnt/optimization/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Optimization Is For Compilers" date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "optimization"] +tags = ["books", "things i learnt", "optimization"] +++ Let say you need more performance on your application. You may be tempted to diff --git a/content/books/things-i-learnt/outside-project/index.md b/content/books/things-i-learnt/outside-project/index.md index a061991..415ccb9 100644 --- a/content/books/things-i-learnt/outside-project/index.md +++ b/content/books/things-i-learnt/outside-project/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Don't Mess With Things Outside Your Proj date = 2019-06-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "frameworks"] +tags = ["books", "things i learnt", "frameworks"] +++ Simple rule: Is the code yours or from your team? Good, you can make any diff --git a/content/books/things-i-learnt/own-your-shit/index.md b/content/books/things-i-learnt/own-your-shit/index.md index 4665078..defb8de 100644 --- a/content/books/things-i-learnt/own-your-shit/index.md +++ b/content/books/things-i-learnt/own-your-shit/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Own Your Shit" date = 2019-07-30 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "own your shit"] +tags = ["books", "things i learnt", "personal", "own your shit"] +++ When I said "Scala is garbage" or "Gerrit is a mistake", it wasn't "l33th4x0r" diff --git a/content/books/things-i-learnt/paper-notes/index.md b/content/books/things-i-learnt/paper-notes/index.md index b33a1dd..5e041fe 100644 --- a/content/books/things-i-learnt/paper-notes/index.md +++ b/content/books/things-i-learnt/paper-notes/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Create Libraries" date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "paper notes", "post its", "project organization"] +tags = ["books", "things i learnt", "paper notes", "post its", "project organization"] +++ I've tried to go paperless many, many times. But keeping a notepad and a bunch diff --git a/content/books/things-i-learnt/patterns-not-solutions/index.md b/content/books/things-i-learnt/patterns-not-solutions/index.md index 1a3e3d2..e1a8fab 100644 --- a/content/books/things-i-learnt/patterns-not-solutions/index.md +++ b/content/books/things-i-learnt/patterns-not-solutions/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Design Patters Are Used to Name Solution date = 2019-06-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "design patterns"] +tags = ["books", "things i learnt", "design patterns"] +++ Most of the times I saw design patterns being applied, they were applied as a diff --git a/content/books/things-i-learnt/people-care/index.md b/content/books/things-i-learnt/people-care/index.md index 3585200..95f6088 100644 --- a/content/books/things-i-learnt/people-care/index.md +++ b/content/books/things-i-learnt/people-care/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - People Get Upset About Code And Architec date = 2019-07-19 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "care"] +tags = ["books", "things i learnt", "personal", "care"] +++ At some point, you'll describe some solution/decision about some piece of diff --git a/content/books/things-i-learnt/permanent-solution/index.md b/content/books/things-i-learnt/permanent-solution/index.md index 2df46c8..7f83fa3 100644 --- a/content/books/things-i-learnt/permanent-solution/index.md +++ b/content/books/things-i-learnt/permanent-solution/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Nothing More Permanent Than A Temporary date = 2019-07-29 [taxonomies] -tags = ["en-au", "books", "things i learnt", "code", "writing code", "temporary solutions"] +tags = ["books", "things i learnt", "code", "writing code", "temporary solutions"] +++ Depending on where you look, "Nothing more permanent than a temporary diff --git a/content/books/things-i-learnt/post-solution/index.md b/content/books/things-i-learnt/post-solution/index.md index 109d259..a89bcb4 100644 --- a/content/books/things-i-learnt/post-solution/index.md +++ b/content/books/things-i-learnt/post-solution/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Blogging About Your Stupid Solution Is S date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "solutions"] +tags = ["books", "things i learnt", "personal", "solutions"] +++ You may think "This project is so small and so focused on whatever I needed, I diff --git a/content/books/things-i-learnt/project-organization/index.md b/content/books/things-i-learnt/project-organization/index.md index 272ac4e..fb3f598 100644 --- a/content/books/things-i-learnt/project-organization/index.md +++ b/content/books/things-i-learnt/project-organization/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Organize Your Code by Data/Type, Not Fun date = 2019-07-15 [taxonomies] -tags = ["en-au", "books", "things i learnt", "project", "project organization"] +tags = ["books", "things i learnt", "project", "project organization"] +++ A lot of projects assume that you'll put things with the same functionality in diff --git a/content/books/things-i-learnt/quit/index.md b/content/books/things-i-learnt/quit/index.md index 338cdd2..09a2736 100644 --- a/content/books/things-i-learnt/quit/index.md +++ b/content/books/things-i-learnt/quit/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Toxic/Aggressive People Are Not Fixable" date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "quit"] +tags = ["books", "things i learnt", "personal", "quit"] +++ Instead of taking the blows and keep moving, maybe it would be better to your diff --git a/content/books/things-i-learnt/resist-easy/index.md b/content/books/things-i-learnt/resist-easy/index.md index 2b4e853..c79840b 100644 --- a/content/books/things-i-learnt/resist-easy/index.md +++ b/content/books/things-i-learnt/resist-easy/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Resist The Temptation Of Easy" date = 2019-07-01 [taxonomies] -tags = ["en-au", "books", "things i learnt", "ides"] +tags = ["books", "things i learnt", "ides"] +++ Sure that IDE will help you with a ton of autocomplete stuff and let you diff --git a/content/books/things-i-learnt/responsible-code/index.md b/content/books/things-i-learnt/responsible-code/index.md index bbccbf9..ca3cf8e 100644 --- a/content/books/things-i-learnt/responsible-code/index.md +++ b/content/books/things-i-learnt/responsible-code/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Take Responsibility For The Use Of Your date = 2019-07-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "responsibility"] +tags = ["books", "things i learnt", "personal", "responsibility"] +++ This is hard. Very very hard. It's the difference between "freedom" and diff --git a/content/books/things-i-learnt/right-tool-agenda/index.md b/content/books/things-i-learnt/right-tool-agenda/index.md index d69c9ea..4d4ba34 100644 --- a/content/books/things-i-learnt/right-tool-agenda/index.md +++ b/content/books/things-i-learnt/right-tool-agenda/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - \"Right Tool For The Job\" Is Just To Pu date = 2019-06-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "right tool", "agenda"] +tags = ["books", "things i learnt", "right tool", "agenda"] +++ A lot of times I heard "We should use the right tool for the job!" Most of diff --git a/content/books/things-i-learnt/right-tool-obvious/index.md b/content/books/things-i-learnt/right-tool-obvious/index.md index 5c68f9b..0bfe646 100644 --- a/content/books/things-i-learnt/right-tool-obvious/index.md +++ b/content/books/things-i-learnt/right-tool-obvious/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - The Right Tool Is More Obvious Than You date = 2019-06-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "right tool"] +tags = ["books", "things i learnt", "right tool"] +++ Maybe you're in a project that needs to process some text. Maybe you're diff --git a/content/books/things-i-learnt/run-locally/index.md b/content/books/things-i-learnt/run-locally/index.md index b073d15..1122b42 100644 --- a/content/books/things-i-learnt/run-locally/index.md +++ b/content/books/things-i-learnt/run-locally/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - If It Doesn't Run On Your Computer, You date = 2019-07-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "local run", "cloud"] +tags = ["books", "things i learnt", "local run", "cloud"] +++ I've seen a lot of systems that would never run on a isolated computer, like diff --git a/content/books/things-i-learnt/say-no/index.md b/content/books/things-i-learnt/say-no/index.md index 614c55b..b054bbd 100644 --- a/content/books/things-i-learnt/say-no/index.md +++ b/content/books/things-i-learnt/say-no/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Learn To Say No" date = 2019-07-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "say no"] +tags = ["books", "things i learnt", "personal", "say no"] +++ Sometimes, you'll have to say no: No, I can't do it; no, it can't be made in diff --git a/content/books/things-i-learnt/small-world/index.md b/content/books/things-i-learnt/small-world/index.md index f1e4f30..9b65608 100644 --- a/content/books/things-i-learnt/small-world/index.md +++ b/content/books/things-i-learnt/small-world/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - I.T. World Is Really Small" date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal"] +tags = ["books", "things i learnt", "personal"] +++ We have two expressions here: "The world turns around"; it means whatever you diff --git a/content/books/things-i-learnt/spec-first/index.md b/content/books/things-i-learnt/spec-first/index.md index b4fdc1a..368b761 100644 --- a/content/books/things-i-learnt/spec-first/index.md +++ b/content/books/things-i-learnt/spec-first/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Spec First, Then Code" date = 2019-06-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "specs", "code"] +tags = ["books", "things i learnt", "specs", "code"] +++ "Without requirements or design, programming is the art of adding bugs to an diff --git a/content/books/things-i-learnt/specialists/index.md b/content/books/things-i-learnt/specialists/index.md index 829e483..963775f 100644 --- a/content/books/things-i-learnt/specialists/index.md +++ b/content/books/things-i-learnt/specialists/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Companies Look For Specialists But Keep date = 2019-07-17 [taxonomies] -tags = ["en-au", "books", "things i learnt", "jobs", "specialists", "generalists"] +tags = ["books", "things i learnt", "jobs", "specialists", "generalists"] +++ If you know a lot about one single language, it may make it easier to get a diff --git a/content/books/things-i-learnt/start-stupid/index.md b/content/books/things-i-learnt/start-stupid/index.md index d313143..8d2a921 100644 --- a/content/books/things-i-learnt/start-stupid/index.md +++ b/content/books/things-i-learnt/start-stupid/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Start Stupid" date = 2019-07-01 [taxonomies] -tags = ["en-au", "books", "things i learnt", "kiss"] +tags = ["books", "things i learnt", "kiss"] +++ One way to get away from the IDE is to "start stupid": Just get the compiler diff --git a/content/books/things-i-learnt/steps-as-comments/index.md b/content/books/things-i-learnt/steps-as-comments/index.md index 56b52c7..1a123fd 100644 --- a/content/books/things-i-learnt/steps-as-comments/index.md +++ b/content/books/things-i-learnt/steps-as-comments/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Write Steps as Comments" date = 2019-06-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "steps", "comments", "code"] +tags = ["books", "things i learnt", "steps", "comments", "code"] +++ Don't know how to solve your problem? Write the steps as comments in your diff --git a/content/books/things-i-learnt/stupid-bugs-list/index.md b/content/books/things-i-learnt/stupid-bugs-list/index.md index c3f19ae..64aead2 100644 --- a/content/books/things-i-learnt/stupid-bugs-list/index.md +++ b/content/books/things-i-learnt/stupid-bugs-list/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Keep A List of Stupid Bugs That Took Mor date = 2019-07-17 [taxonomies] -tags = ["en-au", "books", "things i learnt", "lists", "stupid bugs"] +tags = ["books", "things i learnt", "lists", "stupid bugs"] +++ If it took you more than one hour for you to figure out what went wrong, it is diff --git a/content/books/things-i-learnt/team-discussion/index.md b/content/books/things-i-learnt/team-discussion/index.md index 652eb77..3f7fc01 100644 --- a/content/books/things-i-learnt/team-discussion/index.md +++ b/content/books/things-i-learnt/team-discussion/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Global Changes Must Be Discussed With Th date = 2019-07-31 [taxonomies] -tags = ["en-au", "books", "things i learnt", "team", "changes"] +tags = ["books", "things i learnt", "team", "changes"] +++ So you got tired of bad tests and decided it is a good idea to add some [fuzz diff --git a/content/books/things-i-learnt/tests-apis/index.md b/content/books/things-i-learnt/tests-apis/index.md index 530b17f..a1810b6 100644 --- a/content/books/things-i-learnt/tests-apis/index.md +++ b/content/books/things-i-learnt/tests-apis/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Tests Make Better APIs" date = 2019-06-19 [taxonomies] -tags = ["en-au", "book", "things i learnt", "unit tests", "layers", "apis"] +tags = ["book", "things i learnt", "unit tests", "layers", "apis"] +++ Testing things in isolation may give a better view of your APIs. diff --git a/content/books/things-i-learnt/tests-dead-code/index.md b/content/books/things-i-learnt/tests-dead-code/index.md index 255f30e..4795052 100644 --- a/content/books/things-i-learnt/tests-dead-code/index.md +++ b/content/books/things-i-learnt/tests-dead-code/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Testing Every Function Creates Dead Code date = 2019-06-21 [taxonomies] -tags = ["en-au", "books", "things i learnt", "unit tests", "dead code"] +tags = ["books", "things i learnt", "unit tests", "dead code"] +++ If you write a test for every single function on your system, and your system diff --git a/content/books/things-i-learnt/tests-in-the-command-line/index.md b/content/books/things-i-learnt/tests-in-the-command-line/index.md index 2f29cec..cca9ba8 100644 --- a/content/books/things-i-learnt/tests-in-the-command-line/index.md +++ b/content/books/things-i-learnt/tests-in-the-command-line/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Make Tests That You Know How To Run on t date = 2019-06-19 [taxonomies] -tags = ["en-au", "book", "things i learnt", "tests", "command line"] +tags = ["book", "things i learnt", "tests", "command line"] +++ You know that "Play" with a little something on your IDE that runs only the diff --git a/content/books/things-i-learnt/things-i-dont-know/index.md b/content/books/things-i-learnt/things-i-dont-know/index.md index 3dcb994..e5fbeb0 100644 --- a/content/books/things-i-learnt/things-i-dont-know/index.md +++ b/content/books/things-i-learnt/things-i-dont-know/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Keep A List of Things I Don't Know" date = 2019-07-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "things i don't know", "richard feyman"] +tags = ["books", "things i learnt", "personal", "things i don't know", "richard feyman"] +++ Richard Feymann, famous physicist, kept a notebook with the title "Things I diff --git a/content/books/things-i-learnt/throw-away/index.md b/content/books/things-i-learnt/throw-away/index.md index cd8922a..7b88873 100644 --- a/content/books/things-i-learnt/throw-away/index.md +++ b/content/books/things-i-learnt/throw-away/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Be Ready To Throw Your Code Away" date = 2019-06-19 [taxonomies] -tags = ["en-au", "book", "things i learnt", "code"] +tags = ["book", "things i learnt", "code"] +++ A lot of people, when they start with TDD, get annoyed when you say that you diff --git a/content/books/things-i-learnt/time-to-stop/index.md b/content/books/things-i-learnt/time-to-stop/index.md index 32b46ec..1a81d04 100644 --- a/content/books/things-i-learnt/time-to-stop/index.md +++ b/content/books/things-i-learnt/time-to-stop/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - When It's Time to Stop, It's Time To Sto date = 2019-07-18 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "stop", "personal time"] +tags = ["books", "things i learnt", "personal", "stop", "personal time"] +++ Learn when you can't code anymore. diff --git a/content/books/things-i-learnt/time/index.md b/content/books/things-i-learnt/time/index.md index df9f6fb..0e81de7 100644 --- a/content/books/things-i-learnt/time/index.md +++ b/content/books/things-i-learnt/time/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - You Always Have The Time" date = 2019-07-29 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "time"] +tags = ["books", "things i learnt", "personal", "time"] +++ You may think "Alright, I have a list of things I don't know, but I have no diff --git a/content/books/things-i-learnt/toxic-people/index.md b/content/books/things-i-learnt/toxic-people/index.md index 02f09a6..c44ca7c 100644 --- a/content/books/things-i-learnt/toxic-people/index.md +++ b/content/books/things-i-learnt/toxic-people/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Beware of Toxic People" date = 2019-07-23 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "toxic people"] +tags = ["books", "things i learnt", "personal", "toxic people"] +++ You'll find people that, even if they don't small talk you, they will bad diff --git a/content/books/things-i-learnt/transparent/index.md b/content/books/things-i-learnt/transparent/index.md index b40aa80..e81bf72 100644 --- a/content/books/things-i-learnt/transparent/index.md +++ b/content/books/things-i-learnt/transparent/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Be Transparent With The User" date = 2019-07-31 [taxonomies] -tags = ["en-au", "books", "things i learnt", "ux", "ui"] +tags = ["books", "things i learnt", "ux", "ui"] +++ Since we are talking about [logging](/books/things-i-learnt/log-events), diff --git a/content/books/things-i-learnt/understand-shortcuts/index.md b/content/books/things-i-learnt/understand-shortcuts/index.md index baf704f..36b1c37 100644 --- a/content/books/things-i-learnt/understand-shortcuts/index.md +++ b/content/books/things-i-learnt/understand-shortcuts/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Shortcuts Are nice, But Only In The Shor date = 2019-07-08 [taxonomies] -tags = ["en-au", "books", "things i learnt", "frameworks"] +tags = ["books", "things i learnt", "frameworks"] +++ A lot of languages/libraries/frameworks add a way to make things shorter, diff --git a/content/books/things-i-learnt/units/index.md b/content/books/things-i-learnt/units/index.md index d3225c9..7dadd53 100644 --- a/content/books/things-i-learnt/units/index.md +++ b/content/books/things-i-learnt/units/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Units Makes Things Clear" date = 2019-07-17 [taxonomies] -tags = ["en-au", "books", "things i learnt", "units", "explicit"] +tags = ["books", "things i learnt", "units", "explicit"] +++ You know what's one of the worst function names ever? `sleep()`. diff --git a/content/books/things-i-learnt/use-structures/index.md b/content/books/things-i-learnt/use-structures/index.md index 2b1f7e6..04fefe5 100644 --- a/content/books/things-i-learnt/use-structures/index.md +++ b/content/books/things-i-learnt/use-structures/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - If Your Data Has a Schema, Use a Structu date = 2019-06-25 [taxonomies] -tags = ["en-au", "books", "things i learnt", "data classes", "structs"] +tags = ["books", "things i learnt", "data classes", "structs"] +++ You may be tempted to use a list (or tuple, if your language allows) to keep diff --git a/content/books/things-i-learnt/use-timezones/index.md b/content/books/things-i-learnt/use-timezones/index.md index 6873b8f..1860269 100644 --- a/content/books/things-i-learnt/use-timezones/index.md +++ b/content/books/things-i-learnt/use-timezones/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Always Use Timezones With Your Dates" date = 2019-07-01 [taxonomies] -tags = ["en-au", "books", "things i learnt", "dates", "timezones"] +tags = ["books", "things i learnt", "dates", "timezones"] +++ No matter if the date you're receiving is in your local timezone and you'll diff --git a/content/books/things-i-learnt/use-utf8/index.md b/content/books/things-i-learnt/use-utf8/index.md index 3c7e33d..74be845 100644 --- a/content/books/things-i-learnt/use-utf8/index.md +++ b/content/books/things-i-learnt/use-utf8/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Always Use UTF-8 For Your Strings" date = 2019-07-01 [taxonomies] -tags = ["en-au", "books", "things i learnt", "utf-8"] +tags = ["books", "things i learnt", "utf-8"] +++ Long gone are the days where [ASCII](https://en.wikipedia.org/wiki/ASCII) was diff --git a/content/books/things-i-learnt/users/index.md b/content/books/things-i-learnt/users/index.md index e89601f..0979869 100644 --- a/content/books/things-i-learnt/users/index.md +++ b/content/books/things-i-learnt/users/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Think About The Users" date = 2019-07-17 [taxonomies] -tags = ["en-au", "books", "things i learnt", "privacy"] +tags = ["books", "things i learnt", "privacy"] +++ Think how the data you're collecting from your users will be used -- this is diff --git a/content/books/things-i-learnt/watch-reactions/index.md b/content/books/things-i-learnt/watch-reactions/index.md index 0e31d19..1f9c18c 100644 --- a/content/books/things-i-learnt/watch-reactions/index.md +++ b/content/books/things-i-learnt/watch-reactions/index.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - Pay Attention On How People React To You date = 2019-07-19 [taxonomies] -tags = ["en-au", "books", "things i learnt", "personal", "reactions"] +tags = ["books", "things i learnt", "personal", "reactions"] +++ One way you can learn about yourself is to pay attention on how people react diff --git a/content/code/agile-vs-culture.md b/content/code/agile-vs-culture.md index 1d243f1..be7fb9c 100644 --- a/content/code/agile-vs-culture.md +++ b/content/code/agile-vs-culture.md @@ -1,13 +1,12 @@ +++ title = "Agile vs Culture: The Story of Outliners" date = 2015-12-18 -category = "thoughts" [taxonomies] -tags = ["agile", "book", "empowerment", "disenfranchise", "en-au"] +tags = ["agile", "book", "empowerment", "disenfranchise"] +++ -When the culture goes againt agile. +When the culture goes against agile. diff --git a/content/code/couchbase-example-and-rest.md b/content/code/couchbase-example-and-rest.md index d575d9d..23d69e2 100644 --- a/content/code/couchbase-example-and-rest.md +++ b/content/code/couchbase-example-and-rest.md @@ -1,10 +1,9 @@ +++ title = "Couchbase Example and REST" date = 2016-01-12 -category = "code" [taxonomies] -tags = ["rest", "couchbase", "example", "restful", "en-au"] +tags = ["rest", "couchbase", "example", "restful"] +++ Using the example Couchbase to show how REST works. diff --git a/content/code/dear-github-maintainers.md b/content/code/dear-github-maintainers.md index 3d4796f..a665024 100644 --- a/content/code/dear-github-maintainers.md +++ b/content/code/dear-github-maintainers.md @@ -4,7 +4,7 @@ date = 2016-01-15 categories = "code" [taxonomies] -tags = ["github", "comments", "en-au"] +tags = ["github", "comments"] +++ A rebuttal to "Dear Github". diff --git a/content/code/dont-diminish-types.md b/content/code/dont-diminish-types.md index 19dc738..8fa2c7e 100644 --- a/content/code/dont-diminish-types.md +++ b/content/code/dont-diminish-types.md @@ -1,10 +1,9 @@ +++ title = "Don't Diminish Types" date = 2019-06-03 -categories = "code" [taxonomies] -tags = ["programming languages", "dynamic types", "types", "en-au"] +tags = ["programming languages", "dynamic types", "types"] +++ In a previous life, I had a long discussion on why adding booleans was a bad diff --git a/content/code/lets-not-call-it-unittests-anymore.md b/content/code/lets-not-call-it-unittests-anymore.md index b715b86..d0734d5 100644 --- a/content/code/lets-not-call-it-unittests-anymore.md +++ b/content/code/lets-not-call-it-unittests-anymore.md @@ -1,14 +1,11 @@ +++ - title = "Let's Not Call It \"Unit Tests\" Anymore" date = 2018-05-09 -category = "thoughts" - [taxonomies] -tags = ["unit tests", "en-au"] - +tags = ["unit tests"] +++ + I keep seeing people call tests "integration tests", while they are perfect unit tests. So maybe what we call "unit tests" shouldn't be called unit tests. diff --git a/content/code/mocking-a-mock.md b/content/code/mocking-a-mock.md index 93489b2..921ca06 100644 --- a/content/code/mocking-a-mock.md +++ b/content/code/mocking-a-mock.md @@ -1,10 +1,9 @@ +++ title = "Mocking A Mock" date = 2016-07-21 -category = "code" [taxonomies] -tags = ["python", "mock", "mongodb", "find", "count", "en-au"] +tags = ["python", "mock", "mongodb", "find", "count"] +++ Mocks are an important part of testing, but learn how to properly mock stuff. diff --git a/content/code/on-unittests-and-layers-2.md b/content/code/on-unittests-and-layers-2.md index 2a5a09c..169b5bb 100644 --- a/content/code/on-unittests-and-layers-2.md +++ b/content/code/on-unittests-and-layers-2.md @@ -1,12 +1,9 @@ +++ - title = "On Unit Tests and Layers, Part II" date = 2017-09-15 -category = "code" - [taxonomies] -tags = ["unit tests", "en-au"] +tags = ["unit tests"] +++ After coming with a discussion about unit tests and layers, I got a diff --git a/content/code/on-unittests-and-layers.md b/content/code/on-unittests-and-layers.md index 88f9fef..e327d30 100644 --- a/content/code/on-unittests-and-layers.md +++ b/content/code/on-unittests-and-layers.md @@ -2,10 +2,8 @@ title = "On Unit Tests and Layers" date = 2017-09-11 -category = "code" - [taxonomies] -tags = ["unit tests", "en-au", "testing", "layers"] +tags = ["unit tests", "testing", "layers"] +++ On a recent discussion about testing, I think I came up with a diff --git a/content/code/publishing-books-on-zola.md b/content/code/publishing-books-on-zola.md index 94ba0f2..ee4d398 100644 --- a/content/code/publishing-books-on-zola.md +++ b/content/code/publishing-books-on-zola.md @@ -4,7 +4,7 @@ date = 2019-01-20 category = "thoughts" [taxonomies] -tags = ["en-au", "books", "zola"] +tags = ["books", "zola"] +++ A long time ago I wrote a couple of posts on a WordPress, then moved them to diff --git a/content/code/the-day-i-found-my-old-code.md b/content/code/the-day-i-found-my-old-code.md index 0244eb2..3ed3425 100644 --- a/content/code/the-day-i-found-my-old-code.md +++ b/content/code/the-day-i-found-my-old-code.md @@ -1,10 +1,9 @@ +++ title = "The Day I Found My Old Code" date = 2015-12-18 -category = "code" [taxonomies] -tags = ["code", "python", "pep8", "pylint", "en-au"] +tags = ["code", "python", "pep8", "pylint"] +++ Found a piece of code I wrote 2 years ago, following a lot of linters. I'm diff --git a/content/code/when-i-used-pep8-to-fuck-up-code.md b/content/code/when-i-used-pep8-to-fuck-up-code.md index 5071ff1..42196b2 100644 --- a/content/code/when-i-used-pep8-to-fuck-up-code.md +++ b/content/code/when-i-used-pep8-to-fuck-up-code.md @@ -2,10 +2,8 @@ title = "When I Used PEP8 To Fuck Up Code" date = 2016-07-19 -category = "code" - [taxonomies] -tags = ["python", "pep8", "readability", "en-au"] +tags = ["python", "pep8", "readability"] +++ We "inherited" some Python code recently. Although another team was working on diff --git a/content/code/why-mixing-tabs-and-spaces-is-a-big-deal.md b/content/code/why-mixing-tabs-and-spaces-is-a-big-deal.md index 6190998..12c5f45 100644 --- a/content/code/why-mixing-tabs-and-spaces-is-a-big-deal.md +++ b/content/code/why-mixing-tabs-and-spaces-is-a-big-deal.md @@ -2,10 +2,8 @@ title = "Why Mixing Spaces and Tabs IS a Big Deal" date = 2016-12-15 -category = "code" - [taxonomies] -tags = ["tabs", "spaces", "clean code", "editors", "en-au"] +tags = ["tabs", "spaces", "clean code", "editors"] +++ Why something so small is actually a big deal. diff --git a/content/reviews/books/1001-video-games-you-must-play-before-you-die.md b/content/reviews/books/1001-video-games-you-must-play-before-you-die.md index a7cf523..5ae1a4c 100644 --- a/content/reviews/books/1001-video-games-you-must-play-before-you-die.md +++ b/content/reviews/books/1001-video-games-you-must-play-before-you-die.md @@ -2,23 +2,82 @@ title = "1001 Video Games You Must Play Before You Die - Tony Mott" date = 2015-01-11 -category = "review" - [taxonomies] -tags = ["books", "en-au", "tony mott"] +tags = ["books", "tony mott", "video games", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/8390909-1001-video-games-you-must-play-before-you-die): +For devoted gamers as well as those interested in groundbreaking graphic +design, this is the first, most comprehensive, and only critical guide ever +published to video games. The video game has arrived as entertainment and as +an art form. This is the first serious critical evaluation ever published of +the best video games and is a testament to the medium’s innovativeness and +increasing emphasis on aesthetics. Organized chronologically and for all +platforms (PC, Xbox, PlayStation, etc.) and covering all genres from the bold +(Grand Theft Auto and Halo) and dark (Resident Evil and Silent Hill) to the +spiritual (Final Fantasy) and whimsical (Legend of Zelda), the book traces the +video game from the rough early days of Pong to the latest visual fantasia. + + + {{ stars(stars=2) }} -For a second -- or, at least, the first chapter --, you may believe that this book will discuss 1001 games that influenced the next generation, from the very first pong all the way to the latest Mario. Sadly, it doesn't. +For a second -- or, at least, the first chapter --, you may believe that this +book will discuss 1001 games that influenced the next generation, from the +very first pong all the way to the latest Mario. Sadly, it doesn't. + +The whole problem is that the authors decided to use a chronological order +instead of a topic order. Instead of going "this game introduced this feature" +and then jump to the next which improved that feature, they go into games +released in the 70s, 80s, 90s, 2000s and 2010s. "Where is the harm in that?" +you may ask. Well, the harm is that the chronological order doesn't offer, +most of the time, the reason *why* a game should be played. I mean, yeah, +maybe "Mario World" is not a bad game, but if "Mario World 2" just improves +the old mechanics and have bigger maps, it's clear why the first shouldn't be +in the list if everything from the first I can get in a better form in the +second. + +For example, when they talk about "Ninja Gaiden Black", the authors mention +this: -The whole problem is that the authors decided to use a chronological order instead of a topic order. Instead of going "this game introduced this feature" and then jump to the next which improved that feature, they go into games released in the 70s, 80s, 90s, 2000s and 2010s. "Where is the harm in that?" you may ask. Well, the harm is that the chronological order doesn't offer, most of the time, the reason *why* a game should be played. I mean, yeah, maybe "Mario World" is not a bad game, but if "Mario World 2" just improves the old mechanics and have bigger maps, it's clear why the first shouldn't be in the list if everything from the first I can get in a better form in the second. +> Barring a dodgy camera, Ninja Gaiden didn't have much wrong with it. That +> didn't stop Team Ninja from obsessively tinkering with their masterprice, +> however, and in Ninja Gaiden Black they improved on what many fighting fans +> already regarded as the greatest fighting game of its generation." -For example, when they talk about "Ninja Gaiden Black", the authors mention this:>Barring a dodgy camera, Ninja Gaiden didn't have much wrong with it. That didn't stop Team Ninja from obsessively tinkering with their masterprice, however, and in Ninja Gaiden Black they improved on what many fighting fans already regarded as the greatest fighting game of its generation."And guess what? "Ninja Gaiden" is also in the list! Why would I play the first one when the second is everything the first one has plus more? +And guess what? "Ninja Gaiden" is also in the list! Why would I play the first +one when the second is everything the first one has plus more? -Also, each game have three to four paragraphs. The first is always something related to the game outside it: The company that developed it, some social remark at the time, something in the game culture... anything that it is not the game; the last paragraph try to conclude the (simplistic) review with a positive note; the paragraphs in the middle, which should be the "Why" are not always they "Why". Most of the Mario and Zelda games simply lack the "why". You should play because... you should play? +Also, each game have three to four paragraphs. The first is always something +related to the game outside it: The company that developed it, some social +remark at the time, something in the game culture... anything that it is not +the game; the last paragraph try to conclude the (simplistic) review with a +positive note; the paragraphs in the middle, which should be the "Why" are not +always they "Why". Most of the Mario and Zelda games simply lack the "why". +You should play because... you should play? -This is why I'd prefer a topic order: Mario 1 introduced this, Mario 2 changed this into that... It basically forces the list to have a reason instead of seemingly being a list of "I like it". +This is why I'd prefer a topic order: Mario 1 introduced this, Mario 2 changed +this into that... It basically forces the list to have a reason instead of +seemingly being a list of "I like it". -Also, research seems focused on "games I played" instead of "games that existed". For example, there is "Trine", which I can't call a bad game, but the mechanic of "you play several characters and just jump between them based on their abilities" I can backtrack all the way to "Captain Trueno" on MSX in 1989 -- and I'm not claiming *that's* where this mechanics appeared -- but omitting it seems too much laziness. "Master of Orion", "Dota" (the mod for Warcraft III), "Tetrifast", "King's Valley", "Stunts"... all those are games that I can, from my childhood, bring back as previous examples of some of the recommended games that has the same mechanics and are not listed. But, instead, games with the same mechanics but from bigger publishers are. There is even a game I played on MSX in the 90s that have the *exactly* mechanic listed in "Warioware Inc" but, again, not listed. Heck, even "bananas.bas", part of the MS-DOS 6.0 as an example of how powerful QBasic could be, has the same mechanics as "Death Tank", but the later is listed as some "brilliant mechanic never seen before". +Also, research seems focused on "games I played" instead of "games that +existed". For example, there is "Trine", which I can't call a bad game, but +the mechanic of "you play several characters and just jump between them based +on their abilities" I can backtrack all the way to "Captain Trueno" on MSX in +1989 -- and I'm not claiming *that's* where this mechanics appeared -- but +omitting it seems too much laziness. "Master of Orion", "Dota" (the mod for +Warcraft III), "Tetrifast", "King's Valley", "Stunts"... all those are games +that I can, from my childhood, bring back as previous examples of some of the +recommended games that has the same mechanics and are not listed. But, +instead, games with the same mechanics but from bigger publishers are. There +is even a game I played on MSX in the 90s that have the *exactly* mechanic +listed in "Warioware Inc" but, again, not listed. Heck, even "bananas.bas", +part of the MS-DOS 6.0 as an example of how powerful QBasic could be, has the +same mechanics as "Death Tank", but the later is listed as some "brilliant +mechanic never seen before". -In the end, it seems much more like a list of "games that we, the authors like" than a proper "these games you should play because they describe some advancement in games technology and/or some social discussion about the times when they were released", which turns this into a meaningless e-peen counting (171, by the way). \ No newline at end of file +In the end, it seems much more like a list of "games that we, the authors +like" than a proper "these games you should play because they describe some +advancement in games technology and/or some social discussion about the times +when they were released", which turns this into a meaningless e-peen counting +(171, by the way). diff --git a/content/reviews/books/12-years-a-slave.md b/content/reviews/books/12-years-a-slave.md index 1ab10c5..a1bf412 100644 --- a/content/reviews/books/12-years-a-slave.md +++ b/content/reviews/books/12-years-a-slave.md @@ -2,21 +2,48 @@ title = "12 Years a Slave - Solomon Northup" date = 2015-04-09 -category = "review" - [taxonomies] -tags = ["books", "en-au", "solomon northup"] +tags = ["books", "solomon northup", "reviews", "biography"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18478222-twelve-years-a-slave): +Twelve Years a Slave, sub-title: Narrative of Solomon Northup, citizen of +New-York, kidnapped in Washington city in 1841, and rescued in 1853, from a +cotton plantation near the Red River in Louisiana, is a memoir by Solomon +Northup as told to and edited by David Wilson. It is a slave narrative of a +black man who was born free in New York state but kidnapped in Washington, +D.C., sold into slavery, and kept in bondage for 12 years in Louisiana. He +provided details of slave markets in Washington, D.C. and New Orleans, as well +as describing at length cotton and sugar cultivation on major plantations in +Louisiana. + + + + {{ stars(stars=4) }} -I'll admit that I only bought this book for the morbid curiosity of how much flair the movie added. +I'll admit that I only bought this book for the morbid curiosity of how much +flair the movie added. In my view, not so much. -Sure, there are a few differences: Ford didn't sell Northup just because one fight with Tibeats, but because Ford had bills to pay; it wasn't a single fight with Tibeats, but three; the movie doesn't mention the Christmas days; the movie doesn't show Northup genius fish catcher; the movie doesn't show that, in the end, the guys who captured Northup actually tried to sue him back. +Sure, there are a few differences: Ford didn't sell Northup just because one +fight with Tibeats, but because Ford had bills to pay; it wasn't a single +fight with Tibeats, but three; the movie doesn't mention the Christmas days; +the movie doesn't show Northup genius fish catcher; the movie doesn't show +that, in the end, the guys who captured Northup actually tried to sue him +back. But I believe the core of it was there. Which is impressive. -The book doesn't only dwell in the his enslavement years, but also paint a bit of the historical production and live style of the US in the 1850s. The problem at those points is that it gives the false impression that everything is going alright with him at the time -- but after reading "Ghost Rider", I know people in distress tend to write books like everything is alright at some point. Still, it's weird to read such passages, like it was a matter-of-fact and now part of the life of someone who is not the owner of his own life anymore. - -Also, so parts are so incredible distressing, I had to stop and remind myself that this was *not* a fiction book, but actually the story of a man. \ No newline at end of file +The book doesn't only dwell in the his enslavement years, but also paint a bit +of the historical production and live style of the US in the 1850s. The +problem at those points is that it gives the false impression that everything +is going alright with him at the time -- but after reading "Ghost Rider", I +know people in distress tend to write books like everything is alright at some +point. Still, it's weird to read such passages, like it was a matter-of-fact +and now part of the life of someone who is not the owner of his own life +anymore. + +Also, so parts are so incredible distressing, I had to stop and remind myself +that this was *not* a fiction book, but actually the story of a man. diff --git a/content/reviews/books/21-erros-classicos-da-gestao-de-projetos.md b/content/reviews/books/21-erros-classicos-da-gestao-de-projetos.md index 76e0697..004beef 100644 --- a/content/reviews/books/21-erros-classicos-da-gestao-de-projetos.md +++ b/content/reviews/books/21-erros-classicos-da-gestao-de-projetos.md @@ -2,21 +2,52 @@ title = "21 Erros Clássicos da Gestão de Projetos - Eli Rodrigues" date = 2017-05-10 -category = "review" - [taxonomies] -tags = ["books", "en-au", "eli rodrigues"] +tags = ["books", "pt-br", "eli rodrigues", "gestão", "reviews"] +++ -{{ stars(stars=3) }} -21 erros relacionados com gestão clássica de projetos. Solução: métodos ágeis. Mas me precipito. +[Resumo GoodReads](https://www.goodreads.com/book/show/26082064-21-erros-cl-ssicos-da-gest-o-de-projetos): +Por que projetos fracassam? Embora cada projeto seja uma aventura única e sem +precedentes, muitos falham exatamente pelos mesmos motivos. -Sim, o livro fala sobre 21 erros relacionados com a gestão clássica de projetos, com etapas bem definidas, com prazos já fixados e nenhum aceite de transição. Ou seja, problemas que todo mundo que já teve que trabalhar com gestão em cascata já passou e que são problemas já conhecidos e contornados com soluções em metodologias ágeis. +Este livro traz uma coletânea de 21 erros clássicos, obtidos através de +relatos de mais de mil alunos de gestão de projetos dos mais diversos setores +da economia. Estruturado de forma didática e bem-humorada, apresenta +detalhadamente cada situação, permitindo ao leitor conhecer essas +experiências, em vez de se arriscar apenas com suas próprias. -Um problema do livro, no entanto, é que poucos dos erros tem uma solução -- pelo menos, o livro não cita nada sobre como resolver boa parte dos erros; é como se uma vez que o erro aconteceu, não há mais solução. Um exemplo: um dos capítulos fala sobre porque não se escutam as soluções propostas por pessoas da empresa mesmo ("ouvir a prata da casa"), mas não cita nenhum exemplo de como fazer com que essas pessoas se sintam dispostas a falar, ou como coletar essas informações. Simplesmente, existe o problema de não ouvir pessoas técnicas da empresa. Só isso. + -Outro problema é a seção de exemplos. São sempre cenários catastróficos, colocados para mostrar o pior caso possível em que não há retorno para uma solução viável. - -E, ainda, em um ponto, cita métodos ágeis -- que, como eu falei, foi criado justamente para resolver parte dos problemas citados -- e adicionar que é "gambiarra" (não exatamente com essas palavras). E mais pra frente começa a citar algumas sugestões ("sugestões", não soluções) que são baseadas nos métodos ágeis, principalmente scrum. +{{ stars(stars=3) }} -Deve ser interessante para quem vai gerenciar um projeto para ter ideia do que pode acontecer, mas para quem já vivenciou esses problemas ou já usou outras metodologias, a falta de soluções é preocupante. \ No newline at end of file +21 erros relacionados com gestão clássica de projetos. Solução: métodos ágeis. +Mas me precipito. + +Sim, o livro fala sobre 21 erros relacionados com a gestão clássica de +projetos, com etapas bem definidas, com prazos já fixados e nenhum aceite de +transição. Ou seja, problemas que todo mundo que já teve que trabalhar com +gestão em cascata já passou e que são problemas já conhecidos e contornados +com soluções em metodologias ágeis. + +Um problema do livro, no entanto, é que poucos dos erros tem uma solução -- +pelo menos, o livro não cita nada sobre como resolver boa parte dos erros; é +como se uma vez que o erro aconteceu, não há mais solução. Um exemplo: um dos +capítulos fala sobre porque não se escutam as soluções propostas por pessoas +da empresa mesmo ("ouvir a prata da casa"), mas não cita nenhum exemplo de +como fazer com que essas pessoas se sintam dispostas a falar, ou como coletar +essas informações. Simplesmente, existe o problema de não ouvir pessoas +técnicas da empresa. Só isso. + +Outro problema é a seção de exemplos. São sempre cenários catastróficos, +colocados para mostrar o pior caso possível em que não há retorno para uma +solução viável. + +E, ainda, em um ponto, cita métodos ágeis -- que, como eu falei, foi criado +justamente para resolver parte dos problemas citados -- e adicionar que é +"gambiarra" (não exatamente com essas palavras). E mais pra frente começa a +citar algumas sugestões ("sugestões", não soluções) que são baseadas nos +métodos ágeis, principalmente scrum. + +Deve ser interessante para quem vai gerenciar um projeto para ter ideia do que +pode acontecer, mas para quem já vivenciou esses problemas ou já usou outras +metodologias, a falta de soluções é preocupante. diff --git a/content/reviews/books/23-habitos-anti-procrastinacao-como-deixar-de-ser-preguicoso-e-ter-resultados-em-sua-vida.md b/content/reviews/books/23-habitos-anti-procrastinacao-como-deixar-de-ser-preguicoso-e-ter-resultados-em-sua-vida.md index ef68ea9..2617b21 100644 --- a/content/reviews/books/23-habitos-anti-procrastinacao-como-deixar-de-ser-preguicoso-e-ter-resultados-em-sua-vida.md +++ b/content/reviews/books/23-habitos-anti-procrastinacao-como-deixar-de-ser-preguicoso-e-ter-resultados-em-sua-vida.md @@ -2,15 +2,28 @@ title = "23 Hábitos Anti-Procrastinação: Como Deixar de Ser Preguiçoso e Ter Resultados Em Sua Vida - S.J. Scott" date = 2016-08-08 -category = "review" - [taxonomies] -tags = ["books", "en-au", "s.j. scott"] +tags = ["books", "pt-br", "s.j. scott", "reviews"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/23846012-23-h-bitos-anti-procrastina-o): +APRENDA:: Como Parar de Procrastinar e Conseguir Ajuda Para Os Seus Hábitos +Preguiçosos. + + + {{ stars(stars=2) }} Grande resumo do livro: todos os 23 hábitos são: Siga o Get Things Done (GTD). -Ok, não é tão assim, mas uns 80% dos "hábitos" são. O livro foi construído com a ideia de sequencias de: "Esse é o problema", "Essa é a solução", "Como se acostumar a fazer a solução". Entretanto, boa parte de "Como se acostumar a fazer a solução" é, realmente, o que o GTD sugere fazer para fazer com que as coisas sejam feitas. Inclusive a ideia de pastas dentro de pastas (uma para cada dia do mês, uma para cada mês, fica rotacionando as pastas de dias dentro das pastas de meses) é citada nesse livro -- embora o autor tenha citado, pelo menos, a origem do mesmo (de novo, do GTD). +Ok, não é tão assim, mas uns 80% dos "hábitos" são. O livro foi construído com +a ideia de sequencias de: "Esse é o problema", "Essa é a solução", "Como se +acostumar a fazer a solução". Entretanto, boa parte de "Como se acostumar a +fazer a solução" é, realmente, o que o GTD sugere fazer para fazer com que as +coisas sejam feitas. Inclusive a ideia de pastas dentro de pastas (uma para +cada dia do mês, uma para cada mês, fica rotacionando as pastas de dias dentro +das pastas de meses) é citada nesse livro -- embora o autor tenha citado, pelo +menos, a origem do mesmo (de novo, do GTD). -O livro não é ruim, mas para quem já se preparou para seguir o GTD, boa parte do que foi apresentado já é feito. \ No newline at end of file +O livro não é ruim, mas para quem já se preparou para seguir o GTD, boa parte +do que foi apresentado já é feito. diff --git a/content/reviews/books/a-bug-hunters-diary-a-guided-tour-through-the-wilds-of-software-security.md b/content/reviews/books/a-bug-hunters-diary-a-guided-tour-through-the-wilds-of-software-security.md index 993fc56..d8d34d8 100644 --- a/content/reviews/books/a-bug-hunters-diary-a-guided-tour-through-the-wilds-of-software-security.md +++ b/content/reviews/books/a-bug-hunters-diary-a-guided-tour-through-the-wilds-of-software-security.md @@ -2,15 +2,27 @@ title = "A Bug Hunter's Diary: A Guided Tour Through the Wilds of Software Security - Tobias Klein" date = 2016-10-14 -category = "review" - [taxonomies] -tags = ["books", "en-au", "tobias klein"] +tags = ["books", "tobias klein", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/12746081-a-bug-hunter-s-diary): +Seemingly simple bugs can have drastic consequences, allowing attackers to +compromise systems, escalate local privileges, and otherwise wreak havoc on a +system. + + + {{ stars(stars=4) }} -For a long time you keep hearing things like "don't use this 'cause it can be exploited", but you really never saw something like that being exploited. And then comes this book and shows how someone can use everything you know you can't use to actually call something it wasn't expected to be called. +For a long time you keep hearing things like "don't use this 'cause it can be +exploited", but you really never saw something like that being exploited. And +then comes this book and shows how someone can use everything you know you +can't use to actually call something it wasn't expected to be called. -Confusing? Well, it's a very complex issue that involves the call stack and assembly and registers and all that. But the book goes into length explaining and showing those things (so, yeah, some knowledge of assembly is required). +Confusing? Well, it's a very complex issue that involves the call stack and +assembly and registers and all that. But the book goes into length explaining +and showing those things (so, yeah, some knowledge of assembly is required). -In the end, it's a good book about those "things" you know your shouldn't use, and what happens when you actually use them. \ No newline at end of file +In the end, it's a good book about those "things" you know your shouldn't use, +and what happens when you actually use them. diff --git a/content/reviews/books/a-colher-que-desaparece-e-outras-historias-reais-de-loucura-amor-e-morte-a-partir-dos-elementos-quimicos.md b/content/reviews/books/a-colher-que-desaparece-e-outras-historias-reais-de-loucura-amor-e-morte-a-partir-dos-elementos-quimicos.md index fa58dfa..ecb3c0f 100644 --- a/content/reviews/books/a-colher-que-desaparece-e-outras-historias-reais-de-loucura-amor-e-morte-a-partir-dos-elementos-quimicos.md +++ b/content/reviews/books/a-colher-que-desaparece-e-outras-historias-reais-de-loucura-amor-e-morte-a-partir-dos-elementos-quimicos.md @@ -2,17 +2,46 @@ title = "A Colher que desaparece: e outras histórias reais de loucura, amor e morte a partir dos elementos químicos - Sam Kean" date = 2017-02-18 -category = "review" - [taxonomies] -tags = ["books", "en-au", "sam kean"] +tags = ["books", "pt-br", "sam kean", "reviews", "ciência"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/24266615-a-colher-que-desaparece): +Uma colher que desaparece quando colocada no chá quente, uma bizarra corrida +pelo ouro causada por um elemento (telúrio) que tem cheiro de alho, um poeta +que enlouqueceu ao ingerir lítio para se tratar de uma doença. Sam Kean nos +guia em um passeio pelas mais surpreendentes histórias envolvendo a +descoberta, o uso e a criação dos 118 elementos químicos da tabela periódica. +Pelo caminho, o autor aborda a história dos avanços científicos, desde a +descoberta do átomo até a criação de elementos artificiais, passando pela +invenção da tabela periódica e pelo estudo da radioatividade. Mostra também +como a vida humana se modificou devido ao cobre (usado em moedas por ser +"autoestéril"), ao silício (utilizado na revolução da informática) e ao urânio +(um dos grandes responsáveis pela bomba atômica).A propósito: a colher que +desaparece é feita de gálio, elemento 31 da tabela periódica, metal com a +estranha propriedade de ficar no estado líquido acima de 29ºC, temperatura +inferior à de qualquer cafezinho. + + + {{ stars(stars=3) }} -Quando vemos a tabela períodica, vemos apenas uma coleção de elementos descobertos (e alguns, criados) por humanos. Mas a história por trás dessas descobertas é que os professores nunca contam -- talvez com exceção de Marie Curie e olhe lá. +Quando vemos a tabela períodica, vemos apenas uma coleção de elementos +descobertos (e alguns, criados) por humanos. Mas a história por trás dessas +descobertas é que os professores nunca contam -- talvez com exceção de Marie +Curie e olhe lá. -No livro, são contadas as formas como a tabela períodica e seus componentes foram descobertos e montados. Ou seja, a parte *humana* da física e da química. +No livro, são contadas as formas como a tabela períodica e seus componentes +foram descobertos e montados. Ou seja, a parte *humana* da física e da +química. -Embora seja um ponto interessante de falar sobre física e química, o livro desvaneia demais em vários pontos. Começa com um assunto e, sem concluí-lo, passa para outro e nunca retorna. Sem contar que, em alguns pontos, o autor parece esquecer que as explicações devem ser feitas para não-físicos e acaba gerando conteúdos extremamente complicados de serem entendidos. +Embora seja um ponto interessante de falar sobre física e química, o livro +desvaneia demais em vários pontos. Começa com um assunto e, sem concluí-lo, +passa para outro e nunca retorna. Sem contar que, em alguns pontos, o autor +parece esquecer que as explicações devem ser feitas para não-físicos e acaba +gerando conteúdos extremamente complicados de serem entendidos. -Com alguma revisão para evitar que os assuntos fiquem empilham sem solução e uma revisão na acessibilidade do conteúdo, seria um livro excelente para que várias pessoas deixassem de ver física e química como um bicho de sete cabeças. \ No newline at end of file +Com alguma revisão para evitar que os assuntos fiquem empilham sem solução e +uma revisão na acessibilidade do conteúdo, seria um livro excelente para que +várias pessoas deixassem de ver física e química como um bicho de sete +cabeças. diff --git a/content/reviews/books/a-devils-chaplain.md b/content/reviews/books/a-devils-chaplain.md index 31010fe..45935bc 100644 --- a/content/reviews/books/a-devils-chaplain.md +++ b/content/reviews/books/a-devils-chaplain.md @@ -3,7 +3,7 @@ title = "A Devil's Chaplain: Reflections on Hope, Lies, Science, and Love" date = 2019-07-16 [taxonomies] -tags = ["en-au", "books", "reviews", "richard dawkins"] +tags = ["books", "reviews", "richard dawkins", "history", "biography"] +++ [Goodreads summary](https://www.goodreads.com/book/show/61536.A_Devil_s_Chaplain): diff --git a/content/reviews/books/a-filosofia-explica-as-grandes-questoes-da-humanidade.md b/content/reviews/books/a-filosofia-explica-as-grandes-questoes-da-humanidade.md index 1588677..01659e7 100644 --- a/content/reviews/books/a-filosofia-explica-as-grandes-questoes-da-humanidade.md +++ b/content/reviews/books/a-filosofia-explica-as-grandes-questoes-da-humanidade.md @@ -2,19 +2,47 @@ title = "A Filosofia Explica as Grandes Questões da Humanidade - Clóvis de Barros Filho" date = 2017-06-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "clovis de barros filho"] +tags = ["books", "pt-br", "clovis de barros filho", "reviews", "filosofia"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/18624377-a-filosofia-explica-as-grandes-quest-es-da-humanidade): +O homem é livre? Deus existe? O que é um comportamento ético? Muitas das +questões que acompanham e instigam o Homem através dos tempos são temas deste +livro, A filosofia explica as grandes questões da humanidade, fruto de quase +uma década da experiência bem-sucedida do curso homônimo da Casa do Saber. +Engana-se quem pensa que os assuntos em pauta rendem reflexões herméticas ou +embrenhadas de academicismos. Clóvis de Barros Filho e Júlio Pompeu são +mestres na arte de apresentar a filosofia encarnada na vida, com humor e +exemplos cotidianos sem, no entanto, abrir mão da fidelidade às ideias +centrais de pensadores como Platão, Aristóteles, Hobbes, Maquiavel, Nietzsche +e Foucault. Os autores gostam de dizer que o resultado obtido é algo como um +excelente guia turístico, que aponta grandes atrações e revela aos visitantes +experiências novas e fascinantes. Portanto, se a sua vida tem alguma coisa a +ver com liberdade, felicidade, ética, fé, poder, esperança e conhecimento, +este livro é para você. + + + {{ stars(stars=2) }} -Filosofia é algo complicado para se entender, sempre lidando com "meta" fatores ao invés de tratar do fator em si. +Filosofia é algo complicado para se entender, sempre lidando com "meta" +fatores ao invés de tratar do fator em si. -E quando o autor fica divagando ao invés de explicar as coisas, entender filosofia fica ainda pior. +E quando o autor fica divagando ao invés de explicar as coisas, entender +filosofia fica ainda pior. -O estilo da escrita do livro é o que realmente estraga o prazer de ler. Frases minúsculas, falta de uso de vírgula ao continuar pensamentos (o que te força a voltar e ler de novo, para tentar colocar as vírgulas nos lugares dos pontos para que o pensamento siga seu fluxo normal) e uma completa divagação do assunto (de novo, entrecortado pelas frases minúsculas) faz com que entender o que o autor quer dizer uma tarefa praticamente impossível. +O estilo da escrita do livro é o que realmente estraga o prazer de ler. Frases +minúsculas, falta de uso de vírgula ao continuar pensamentos (o que te força a +voltar e ler de novo, para tentar colocar as vírgulas nos lugares dos pontos +para que o pensamento siga seu fluxo normal) e uma completa divagação do +assunto (de novo, entrecortado pelas frases minúsculas) faz com que entender o +que o autor quer dizer uma tarefa praticamente impossível. -A sorte é que o último 1/3 do livro foi escrito por outro autor e nesse ponto sim as coisas fazem sentido. Finalmente começa-se do princípio, vai-se ao meio e termina-se no fim, ao invés de abrir 15 princípios no meio e nunca chegar a um fim. +A sorte é que o último 1/3 do livro foi escrito por outro autor e nesse ponto +sim as coisas fazem sentido. Finalmente começa-se do princípio, vai-se ao meio +e termina-se no fim, ao invés de abrir 15 princípios no meio e nunca chegar a +um fim. -Vale pelo último 1/3, o resto é uma baderna de ser lido sem que se chegue a uma conclusão. \ No newline at end of file +Vale pelo último 1/3, o resto é uma baderna de ser lido sem que se chegue a +uma conclusão. diff --git a/content/reviews/books/a-garota-no-trem.md b/content/reviews/books/a-garota-no-trem.md index 3c86adc..b3182f0 100644 --- a/content/reviews/books/a-garota-no-trem.md +++ b/content/reviews/books/a-garota-no-trem.md @@ -2,17 +2,41 @@ title = "A Garota no Trem - Paula Hawkins" date = 2017-03-18 -category = "review" - [taxonomies] -tags = ["books", "en-au", "paula hawkins"] +tags = ["books", "paula hawkins", "reviews", "ficção", "pt-br"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/25758236-a-garota-no-trem): +Todas as manhãs Rachel pega o trem das 8h04 de Ashbury para Londres. O +arrastar trepidante pelos trilhos faz parte de sua rotina. O percurso, que ela +conhece de cor, é um hipnotizante passeio de galpões, caixas d’água, pontes e +aconchegantes casas. + +Em determinado trecho, o trem para no sinal vermelho. E é de lá que Rachel +observa diariamente a casa de número 15. Obcecada com seus belos habitantes – +a quem chama de Jess e Janson –, Rachel é capaz de descrever o que imagina ser +a vida perfeita do jovem casal. Até testemunhar uma cena chocante, segundos +antes de o trem dar um solavanco e seguir viagem. Poucos dias depois, ela +descobre que Jess – na verdade Megan – está desaparecida. + + + {{ stars(stars=4) }} Mais um "resolvi ler o filme". -Sem partir para spoilers, o livro é interessante mais pela estrutura do que pelo conteúdo. Não que o conteúdo seja ruim, mas é levemente cliché. +Sem partir para spoilers, o livro é interessante mais pela estrutura do que +pelo conteúdo. Não que o conteúdo seja ruim, mas é levemente cliché. -A estrutura, no entando, é bem mais complexa. Segue a vida de três mulheres (uma delas, a principal, "a garota no trem"), contando como a história das três se interage e como forma uma rede só. O problema é que, além de quebrar eventos em três versões diferentes, três pontos de vista diferentes -- algo que eu acho realmente interessante -- os eventos não ocorrem em ordem cronológica. Um capítulo é sobre a mulher 1, em um dia de julho de 2013; o próximo é da mulher 3 em janeiro de 2012; e assim por diante. Como os capítulos são meio longos, às vezes foi preciso voltar pra tentar conectar os espaços temporais para ter a visão do todo da história. +A estrutura, no entando, é bem mais complexa. Segue a vida de três mulheres +(uma delas, a principal, "a garota no trem"), contando como a história das +três se interage e como forma uma rede só. O problema é que, além de quebrar +eventos em três versões diferentes, três pontos de vista diferentes -- algo +que eu acho realmente interessante -- os eventos não ocorrem em ordem +cronológica. Um capítulo é sobre a mulher 1, em um dia de julho de 2013; o +próximo é da mulher 3 em janeiro de 2012; e assim por diante. Como os +capítulos são meio longos, às vezes foi preciso voltar pra tentar conectar os +espaços temporais para ter a visão do todo da história. -Fora isso, é um excelente mistério, com uma boa percepção dos clichés e como utilizá-los para criar plot twists. \ No newline at end of file +Fora isso, é um excelente mistério, com uma boa percepção dos clichés e como +utilizá-los para criar plot twists. diff --git a/content/reviews/books/a-historia-do-mundo-para-quem-tem-pressa.md b/content/reviews/books/a-historia-do-mundo-para-quem-tem-pressa.md index 1fe7580..002170d 100644 --- a/content/reviews/books/a-historia-do-mundo-para-quem-tem-pressa.md +++ b/content/reviews/books/a-historia-do-mundo-para-quem-tem-pressa.md @@ -2,15 +2,43 @@ title = "A História do Mundo Para Quem Tem Pressa - Emma Marriott" date = 2016-05-10 -category = "review" - [taxonomies] -tags = ["books", "en-au", "emma marriott"] +tags = ["books", "pt-br", "emma marriott", "história", "review"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/25543485-a-hist-ria-do-mundo-para-quem-tem-pressa): +Um guia conciso e abrangente, ilustrado por mapas, para tudo o que +necessitamos saber sobre os acontecimentos mais importantes da história, desde +as antigas civilizações (Suméria, Egito e Babilônia, por exemplo) até o final +da Segunda Guerra Mundial. Esteja o leitor interessado no império de +Alexandre, o Grande ou no florescimento da república cartaginesa e sua +destruição por Roma na ascesão dos califados árabes ou na dinastia Tang, da +China, na Guerra Civil norte-americana ou nos povos maia, inca e asteca, +encontrará os fatos essenciais nesta obra igualmente essencial. + + + {{ stars(stars=5) }} -"A História do Mundo Para Quem Tem Pressa" teve uma proposta inicial interessante: contar, resumidamente, o resumo da história em apenas 200 páginas. Embora interessante, o resultado é, no mínimo, curioso: Quando o livro fala de civilizações grandiosas (com os fenícios), cuja cultura se estende por séculos, sendo um dos maiores centros de comércio da época, em apenas um parágrafo, a questão que fica é se era realmente o maior, pra caber em tão pouco espaço; ao mesmo tempo, leva a questão se analisamos a grandeza de uma civilização pelo número de parágrafos ou pelo conteúdo dos parágrafos. +"A História do Mundo Para Quem Tem Pressa" teve uma proposta inicial +interessante: contar, resumidamente, o resumo da história em apenas 200 +páginas. Embora interessante, o resultado é, no mínimo, curioso: Quando o +livro fala de civilizações grandiosas (com os fenícios), cuja cultura se +estende por séculos, sendo um dos maiores centros de comércio da época, em +apenas um parágrafo, a questão que fica é se era realmente o maior, pra caber +em tão pouco espaço; ao mesmo tempo, leva a questão se analisamos a grandeza +de uma civilização pelo número de parágrafos ou pelo conteúdo dos parágrafos. -De qualquer forma, o livro vai desde o ano 5000 a.C. até 1950 d.C., citando as várias civilizações que surgiram, o conhecimento que temos, hoje, dessas civilizações, e a sua repercussão. No entanto, como o livro se divide em períodos de tempos, algumas vezes a história de uma civilização -- e suas ramificações -- fica "cortada" no percorrer do livro. Talvez fosse mais interessante pegar uma civilização e seguir o progresso da mesma desde a sua primeira aparição -- no seu primeiro estado -- e seguir até os dias de hoje, passando por suas transformações. +De qualquer forma, o livro vai desde o ano 5000 a.C. até 1950 d.C., citando as +várias civilizações que surgiram, o conhecimento que temos, hoje, dessas +civilizações, e a sua repercussão. No entanto, como o livro se divide em +períodos de tempos, algumas vezes a história de uma civilização -- e suas +ramificações -- fica "cortada" no percorrer do livro. Talvez fosse mais +interessante pegar uma civilização e seguir o progresso da mesma desde a sua +primeira aparição -- no seu primeiro estado -- e seguir até os dias de hoje, +passando por suas transformações. -No fim, o livro se torna divertido mesmo nos tempos modernos, onde a abundância de informações permite uma maior "manobrabilidade" do conteúdo. Mas, como tido no começo, o livro sofre com a própria ideia de ser um livro de história com 200 páginas e acaba sacrificando o entendimento em alguns casos. \ No newline at end of file +No fim, o livro se torna divertido mesmo nos tempos modernos, onde a +abundância de informações permite uma maior "manobrabilidade" do conteúdo. +Mas, como tido no começo, o livro sofre com a própria ideia de ser um livro de +história com 200 páginas e acaba sacrificando o entendimento em alguns casos. diff --git a/content/reviews/books/all-quiet-on-the-western-front.md b/content/reviews/books/all-quiet-on-the-western-front.md index 7c3c461..79b32ab 100644 --- a/content/reviews/books/all-quiet-on-the-western-front.md +++ b/content/reviews/books/all-quiet-on-the-western-front.md @@ -2,21 +2,47 @@ title = "All Quiet on the Western Front - Erich Maria Remarque" date = 2014-12-24 -category = "review" - [taxonomies] -tags = ["books", "en-au", "erich maria remarque"] +tags = ["books", "erich maria remarque", "reviews", "fiction"] +++ -{{ stars(stars=5) }} -I was sure that in the forewords there was something about "this is not a book to promote war" or anything of the sorts. But alas, the forewords are +[GoodReads Summary](https://www.goodreads.com/book/show/355697.All_Quiet_on_the_Western_Front): +In 1914 a room full of German schoolboys, fresh-faced and idealistic, are +goaded by their schoolmaster to troop off to the ‘glorious war’. With the fire +and patriotism of youth they sign up. What follows is the moving story of a +young ‘unknown soldier’ experiencing the horror and disillusionment of life in +the trenches. ->This book is to be neither an accusation nor a confession, and least of all an adventure, for death is not an adventure to those who stand face to face with it. It will try simply to tell of a generation of men who, even though they may have escaped shells, were destroyed by the war. + -... which basically describes the whole book. +{{ stars(stars=5) }} + +I was sure that in the forewords there was something about "this is not a book +to promote war" or anything of the sorts. But alas, the forewords are -The book follows the story of a young German soldier from the beginning of World War I till almost its end. In following him, we learn how training was, how going to the battle front was like, how friendships were forged, how soldiers survived with the small support from the higher ups, how the rest of the society view and treated those who were in the front and how society lived while the war was raging. +> This book is to be neither an accusation nor a confession, and least of all +> an adventure, for death is not an adventure to those who stand face to face +> with it. It will try simply to tell of a generation of men who, even though +> they may have escaped shells, were destroyed by the war. -Again, my surprise was the "promote war" foreword that I thought existed. 'Cause the book goes far away from it. From it's gory description of the battles, from it's depressing tales of how the society lived, from the sad state most were left when the tides of war changed against those fighting, to the complete desolation of describing how it is to lose someone who fought and helped others in the front, this is far from being a "promotion" of war; if such, it's more of a long story about how governments would engage war without worrying with the poor souls (real people!) who actually got guns in their guns and run against other poor souls that also didn't appear as a single bleep in their government plans. +... which basically describes the whole book. -It's a brutal, sad description of what war really yes. \ No newline at end of file +The book follows the story of a young German soldier from the beginning of +World War I till almost its end. In following him, we learn how training was, +how going to the battle front was like, how friendships were forged, how +soldiers survived with the small support from the higher ups, how the rest of +the society view and treated those who were in the front and how society lived +while the war was raging. + +Again, my surprise was the "promote war" foreword that I thought existed. +'Cause the book goes far away from it. From it's gory description of the +battles, from it's depressing tales of how the society lived, from the sad +state most were left when the tides of war changed against those fighting, to +the complete desolation of describing how it is to lose someone who fought and +helped others in the front, this is far from being a "promotion" of war; if +such, it's more of a long story about how governments would engage war without +worrying with the poor souls (real people!) who actually got guns in their +guns and run against other poor souls that also didn't appear as a single +bleep in their government plans. + +It's a brutal, sad description of what war really yes. diff --git a/content/reviews/books/all-you-need-is-kill.md b/content/reviews/books/all-you-need-is-kill.md index d9d293a..e657d00 100644 --- a/content/reviews/books/all-you-need-is-kill.md +++ b/content/reviews/books/all-you-need-is-kill.md @@ -2,17 +2,38 @@ title = "All You Need Is Kill - Hiroshi Sakurazaka" date = 2014-12-03 -category = "review" - [taxonomies] -tags = ["books", "en-au", "hiroshi sakurazaka"] +tags = ["books", "hiroshi sakurazaka", "reviews", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/6255949-all-you-need-is-kill): +When the alien Gitai invade, Keiji Kiriya is just one of many raw recruits +shoved into a suit of battle armor and sent out to kill. Keiji dies on the +battlefield, only to find himself reborn each morning to fight and die again +and again. On the 158th iteration though, he sees something different, +something out of place: the female soldier known as the Bitch of War. Is the +Bitch the key to Keiji’s escape, or to his final death? + + + {{ stars(stars=4) }} -I admit I got this book because of "Edge of Tomorrow", which I watched before reading the book. As usual, only the concept of the story is the same in both. Apart from "soldier keeps repeating the same day over and over again due alien technology", there is absolutely nothing in common with the movie. +I admit I got this book because of "Edge of Tomorrow", which I watched before +reading the book. As usual, only the concept of the story is the same in both. +Apart from "soldier keeps repeating the same day over and over again due alien +technology", there is absolutely nothing in common with the movie. -The story starts slowly, mostly because Keiji Kiriya is still a fresh guy. But he still kills one special alien and gains temporal superpowers. When that happens, the story picks up and it's really hard to drop it. Then the story stops to tell the backstory of Rita Vrataski and the pace drops a bit; then it goes back to the fight and it picks up again. That's probably how I read this thing so fast. +The story starts slowly, mostly because Keiji Kiriya is still a fresh guy. But +he still kills one special alien and gains temporal superpowers. When that +happens, the story picks up and it's really hard to drop it. Then the story +stops to tell the backstory of Rita Vrataski and the pace drops a bit; then it +goes back to the fight and it picks up again. That's probably how I read this +thing so fast. -In a way, the book is more brutal than the movie, as much as "Jarhead" the book is more brutal than "Jarhead" the movie. Also, the explanation for the "time travel" -- which in the book is no time travel at all, being much more akin to the way Kitty Pride sends people in the time in "X-Men: Days of Future Past" -- seems much more plausible than the movie. +In a way, the book is more brutal than the movie, as much as "Jarhead" the +book is more brutal than "Jarhead" the movie. Also, the explanation for the +"time travel" -- which in the book is no time travel at all, being much more +akin to the way Kitty Pride sends people in the time in "X-Men: Days of Future +Past" -- seems much more plausible than the movie. -It is a short but interesting story, nonetheless. \ No newline at end of file +It is a short but interesting story, nonetheless. diff --git a/content/reviews/books/american-gods.md b/content/reviews/books/american-gods.md index 83d9242..b7e230a 100644 --- a/content/reviews/books/american-gods.md +++ b/content/reviews/books/american-gods.md @@ -2,15 +2,33 @@ title = "American Gods - Neil Gaiman" date = 2015-04-04 -category = "review" - [taxonomies] -tags = ["books", "en-au", "neil gaiman"] +tags = ["books", "neil gaiman", "reviews", "fiction", "american gods"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/30165203-american-gods): +Days before his release from prison, Shadow's wife, Laura, dies in a +mysterious car crash. Numbly, he makes his way back home. On the plane, he +encounters the enigmatic Mr Wednesday, who claims to be a refugee from a +distant war, a former god and the king of America. + +Together they embark on a profoundly strange journey across the heart of the +USA, whilst all around them a storm of preternatural and epic proportions +threatens to break. + + + {{ stars(stars=5) }} **A very hard book to read ** -When I was halfway through it, I though I'd give this book 4 stars; when I was 3/4 through it, I though about giving it only 3 stars; then, in the very end, I decided to give 5 stars. +When I was halfway through it, I though I'd give this book 4 stars; when I was +3/4 through it, I though about giving it only 3 stars; then, in the very end, +I decided to give 5 stars. -Thing is, this is not an easy book to read. It's freaking hard, opening several threads at once, which give the feel that you're reading things that make absolutely nothing to the story. And then, in the very end, all threads are neatly closed. If you manage to keep up to the continuous words that feel worthless and read till the end, you'll get a nicely packaged story, worth your time. \ No newline at end of file +Thing is, this is not an easy book to read. It's freaking hard, opening +several threads at once, which give the feel that you're reading things that +make absolutely nothing to the story. And then, in the very end, all threads +are neatly closed. If you manage to keep up to the continuous words that feel +worthless and read till the end, you'll get a nicely packaged story, worth +your time. diff --git a/content/reviews/books/an-illustrated-book-of-bad-arguments.md b/content/reviews/books/an-illustrated-book-of-bad-arguments.md index ef25ee4..e901c46 100644 --- a/content/reviews/books/an-illustrated-book-of-bad-arguments.md +++ b/content/reviews/books/an-illustrated-book-of-bad-arguments.md @@ -2,17 +2,29 @@ title = "An Illustrated Book of Bad Arguments - Ali Almossawi" date = 2015-03-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ali almossawi"] +tags = ["books", "ali almossawi", "reviews", "logic", "fallacies"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18753581-an-illustrated-book-of-bad-arguments): +This book is aimed at newcomers to the field of logical reasoning, +particularly those who, to borrow a phrase from Pascal, are so made that they +understand best through visuals. I have selected a small set of common errors +in reasoning and visualized them using memorable illustrations that are +supplemented with lots of examples. The hope is that the reader will learn +from these pages some of the most common pitfalls in arguments and be able to +identify and avoid them in practice. + + + {{ stars(stars=4) }} Short, but fun. -It's a really fun read, but really really short (I managed to read the whole thing in about 40 minutes). I expected a little bit more, some more examples, some other types of fallacies and so on. +It's a really fun read, but really really short (I managed to read the whole +thing in about 40 minutes). I expected a little bit more, some more examples, +some other types of fallacies and so on. It's not that the book is bad, quite the contrary. It's a fun read. -But short. \ No newline at end of file +But short. diff --git a/content/reviews/books/angularjs.md b/content/reviews/books/angularjs.md index 788ccf4..6b02f27 100644 --- a/content/reviews/books/angularjs.md +++ b/content/reviews/books/angularjs.md @@ -2,11 +2,20 @@ title = "AngularJS - Brad Green" date = 2014-07-19 -category = "review" - [taxonomies] -tags = ["books", "en-au", "brad green"] +tags = ["books", "brad green", "javascript", "angularjs", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/16087709-angularjs): +Develop smaller, lighter web apps that are simple to create and easy to test, +extend, and maintain as they grow. This hands-on guide introduces you to +AngularJS, the open source JavaScript framework that uses +Model–view–controller (MVC) architecture, data binding, client-side templates, +and dependency injection to create a much-needed structure for building web +apps. + + + {{ stars(stars=2) }} -Teaches the basic, but it's really out of date. \ No newline at end of file +Teaches the basic, but it's really out of date. diff --git a/content/reviews/books/answers-to-questions-youve-never-asked.md b/content/reviews/books/answers-to-questions-youve-never-asked.md index 51821db..ee1d8d7 100644 --- a/content/reviews/books/answers-to-questions-youve-never-asked.md +++ b/content/reviews/books/answers-to-questions-youve-never-asked.md @@ -2,10 +2,8 @@ title = "Answers to Questions You’ve Never Asked: Explaining the What If in Science, Geography and the Absurd - Joseph Pisenti" date = 2018-12-04 -category = "reviews" - [taxonomies] -tags = ["books", "en-au", "trivia", "joseph pisenti"] +tags = ["books", "trivia", "joseph pisenti", "science", "geography", "reviews"] +++ [GoodReads summary](https://www.goodreads.com/book/show/36049427-answers-to-questions-you-ve-never-asked): diff --git a/content/reviews/books/antifragile-systems-and-teams.md b/content/reviews/books/antifragile-systems-and-teams.md index ae6d66c..026c34a 100644 --- a/content/reviews/books/antifragile-systems-and-teams.md +++ b/content/reviews/books/antifragile-systems-and-teams.md @@ -2,15 +2,26 @@ title = "Antifragile Systems and Teams - Dave Zwieback" date = 2017-04-17 -category = "review" - [taxonomies] -tags = ["books", "en-au", "dave zwieback"] +tags = ["books", "dave zwieback", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/22466476-antifragile-systems-and-teams): +All complex computer systems eventually break, despite all of the +heavy-handed, bureaucratic change-management processes we throw at them. But +some systems are clearly more fragile than others, depending on how well they +cope with stress. In this O’Reilly report, Dave Zwieback explains how the +DevOps methodology can help make your system antifragile. + + + {{ stars(stars=2) }} Not really a book, just a paper. But a badly constructed paper. -It doesn't describe what an "antifragile system" is in deep (ok, it's a paper); lists only two examples of antifragile systems; focus too much on devops. +It doesn't describe what an "antifragile system" is in deep (ok, it's a +paper); lists only two examples of antifragile systems; focus too much on +devops. -Sadly, nothing useful -- something you can take with you and use when building your own system or leading your team -- in this. \ No newline at end of file +Sadly, nothing useful -- something you can take with you and use when building +your own system or leading your team -- in this. diff --git a/content/reviews/books/antologia-da-maldade-um-dicionario-de-citacoes-associacoes-ilicitas-e-ligacoes-perigosas.md b/content/reviews/books/antologia-da-maldade-um-dicionario-de-citacoes-associacoes-ilicitas-e-ligacoes-perigosas.md index 2b8f422..65b9a75 100644 --- a/content/reviews/books/antologia-da-maldade-um-dicionario-de-citacoes-associacoes-ilicitas-e-ligacoes-perigosas.md +++ b/content/reviews/books/antologia-da-maldade-um-dicionario-de-citacoes-associacoes-ilicitas-e-ligacoes-perigosas.md @@ -2,13 +2,50 @@ title = "Antologia da maldade: Um Dicionário de Citações, Associações Ilícitas e Ligações Perigosas - Gustavo H. B. Franco" date = 2016-03-19 -category = "review" - [taxonomies] -tags = ["books", "en-au", "gustavo h. b. franco"] +tags = ["books", "pt-br", "gustavo h. b. franco", "reviews", "citações"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/27871962-antologia-da-maldade): +Um livro que reúne o humor, a sabedoria - e a maldade - de figuras +proeminentes do cenário brasileiro e universal, de ontem e hoje. Os +economistas Gustavo Franco e Fabio Giambiagi organizam essa antologia de +citações cujo mote central são frases com dois dedos de maldade. Mas a maldade +que dá título ao livro não é a da perversidade e a da má índole, mas um +composto formado de maldade espirituosa, malícia, atrevimento, ironia, de +alguns maus ditos e de muito bom humor. Estão no livro citações de Nelson +Rodrigues, Millôr Fernandes, Machado de Assis, Getúlio Vargas, Winston +Churchill, Roberto Campos, Shakespeare, Jorge Luis Borges, e muitos outros, +entre banqueiros, políticos, consultores, empresários, artistas, escritores, +esportistas, filósofos, dramaturgos e cientistas. E constam também as falas de +algumas lideranças como Fernando Henrique Cardoso, Luiz Inácio Lula da Silva e +Dilma Rousseff, sem os quais nenhuma coletânea sobre a atualidade estaria +completa. Dividida por temas e organizada em ordem alfabética, a antologia +apresenta mais de setecentos verbetes, preenchidos com observações originais, +inusitadas, afiadas e divertidas sobre praticamente tudo. Encontraremos os +convencionais "Capitalismo", "Socialismo", "Amizade", "Inflação", "Traição", +"Religião", mas também outros singulares, como "Controle da mídia", +"Corrupção", "Groucho-marxismo", "Brasilidade", "Mensalão" e "Petrolão", que +estão no cerne das grandes polêmicas contemporâneas no Brasil. Inflação: +"Queremos apenas reduzir uma inflação indecente de 220% para um nível não +menos indecente de 150%, e depois o próximo governo continuará a luta." +Antonio Delfim Netto, economista e ex-ministro da Fazenda, em 1984. Inveja: "O +melhor dos bens é o que não se possui." Machado de Assis, escritor. Mineirice: +"Em Minas Gerais, a política é como crochê: não se pode dar um ponto errado, +sob pena de ter de começar tudo de novo." Itamar Franco, ex-presidente da +República. + + + + {{ stars(stars=2) }} -Com o título principal de "Antologia da maldade", eu esperava uma lista de citações ácidas de pessoas famosas, como praticamente todas as citações de Winston Churchil. Infelizmente, o livro é apenas mais um livro de citações randômicas, incluindo Mário Quintana, que provavelmente é a única pessoa cujas citações são sempre simpáticas e amáveis. +Com o título principal de "Antologia da maldade", eu esperava uma lista de +citações ácidas de pessoas famosas, como praticamente todas as citações de +Winston Churchil. Infelizmente, o livro é apenas mais um livro de citações +randômicas, incluindo Mário Quintana, que provavelmente é a única pessoa cujas +citações são sempre simpáticas e amáveis. -Assim, de "maldade" há muito pouco, a não ser que seja considerada maldade reproduzir citações de Nelson Rodrigues, cuja existência deveria ser atirada no passado negro do Brasil junto com a ditadura. \ No newline at end of file +Assim, de "maldade" há muito pouco, a não ser que seja considerada maldade +reproduzir citações de Nelson Rodrigues, cuja existência deveria ser atirada +no passado negro do Brasil junto com a ditadura. diff --git a/content/reviews/books/apache-kafka.md b/content/reviews/books/apache-kafka.md index b5b8691..121c011 100644 --- a/content/reviews/books/apache-kafka.md +++ b/content/reviews/books/apache-kafka.md @@ -2,11 +2,21 @@ title = "Apache Kafka - Nishant Garg" date = 2017-07-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "nishant garg"] +tags = ["books", "nishant garg", "reviews", "it", "big data"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18702022-apache-kafka): +The book will follow a step-by-step tutorial approach which will show the +readers how to use Apache Kafka for messaging from scratch.Apache Kafka is for +readers with software development experience, but no prior exposure to Apache +Kafka or similar technologies is assumed. This book is also for enterprise +application developers and big data enthusiasts who have worked with other +publisher-subscriber based systems and now want to explore Apache Kafka as a +futuristic scalable solution. (less) + + + {{ stars(stars=1) }} After reading the book, I ended up with more questions than I had when I started reading: @@ -18,6 +28,14 @@ After reading the book, I ended up with more questions than I had when I started 5. What is a topic? 6. How to create a pipeline to process information, in a way that I have multiple lines of processing? -Not only the book goes straight to "You install this way, you write a simple app, and that's it", it uses some very terse phrases, which makes really hard to read. Things like "This, at times, leads to redevelopment of information producers or consumers to provide an integration point between them", which is terse but has absolutely no information at all. There is even an introduction to Hadoop as "Resource sharing, stability, availability, and scalability are a few of the many challenges of distributed computing. Nowadays, an additional challenge is to process extremely large volumes of data in TBs or PBs." -- which says absolutely NOTHING about what Hadoop is and how it works. +Not only the book goes straight to "You install this way, you write a simple +app, and that's it", it uses some very terse phrases, which makes really hard +to read. Things like "This, at times, leads to redevelopment of information +producers or consumers to provide an integration point between them", which is +terse but has absolutely no information at all. There is even an introduction +to Hadoop as "Resource sharing, stability, availability, and scalability are a +few of the many challenges of distributed computing. Nowadays, an additional +challenge is to process extremely large volumes of data in TBs or PBs." -- +which says absolutely NOTHING about what Hadoop is and how it works. -Again, if you want to know *less* about Kafka, that's a good book for it. \ No newline at end of file +Again, if you want to know *less* about Kafka, that's a good book for it. diff --git a/content/reviews/books/argo.md b/content/reviews/books/argo.md index f10ab3f..6f1b2c7 100644 --- a/content/reviews/books/argo.md +++ b/content/reviews/books/argo.md @@ -5,20 +5,52 @@ date = 2017-04-17 category = "review" [taxonomies] -tags = ["books", "en-au", "antonio j. mendez"] +tags = ["books", "pt-br", "antonio j. mendez", "reviews", "history", "biography", "história", "biografia"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/16252385-argo): +Em 4 de novembro de 1979, os funcionários da embaixada dos Estados Unidos em +Teerã são surpreendidos pela invasão de um grupo de militantes, que faz 53 +reféns. Em meio à confusão, seis diplomatas conseguem escapar e encontram +refúgio na residência do embaixador do Canadá. Mas Tony Mendez, especialista +em disfarces da CIA, sabe perfeitamente que é apenas uma questão de tempo até +que sejam encontrados. Para retirá-los do país, ele concebe um plano muito +arriscado, digno de cinema. Disfarçando-se de produtor de Hollywood e apoiado +por um elenco de agentes secretos, falsificadores e especialistas em efeitos +especiais, Mendez viaja para Teerã a pretexto de encontrar a locação perfeita +para um falso filme de ficção científica chamado Argo. + + + {{ stars(stars=3) }} -Mais um para a lista do "li um filme". Obviamente, o filme é baseado no livro e não o contrário. +Mais um para a lista do "li um filme". Obviamente, o filme é baseado no livro +e não o contrário. -Ao contrário do filme, o livro passa um bom tempo explicando os fatos que levaram à invasão da embaixada americana em Teerã, ao invés de pular diretamente para o resgate -- o que é excelente para entender exatamente porque a embaixada foi invadida. Praticamente a primeira metade do livro inteiro conta os fatos que levaram à invasão, como seis funcionários da embaixada escaparam e por onde passaram até chegar a embaixada canadense. +Ao contrário do filme, o livro passa um bom tempo explicando os fatos que +levaram à invasão da embaixada americana em Teerã, ao invés de pular +diretamente para o resgate -- o que é excelente para entender exatamente +porque a embaixada foi invadida. Praticamente a primeira metade do livro +inteiro conta os fatos que levaram à invasão, como seis funcionários da +embaixada escaparam e por onde passaram até chegar a embaixada canadense. -A segunda metade do livro é que foca na operação de extração (exfiltração) dos funcionários. E não, não foi todo aquela sucessão de eventos que acontece no filme: é bem mais simples do que é mostrado. +A segunda metade do livro é que foca na operação de extração (exfiltração) dos +funcionários. E não, não foi todo aquela sucessão de eventos que acontece no +filme: é bem mais simples do que é mostrado. Entretanto, existem dois grandes problemas do livro: -O primeiro é que Mendez parece super envolvido na sua função de espião da CIA, no clássico "faço tudo pelo meu país", batendo no peito, mas mostra-se de certa forma indignado quando comenta que outros países fazem o mesmo. O clássico, "não confio em ninguém, mas fico indignado quando não confiam em mim." +O primeiro é que Mendez parece super envolvido na sua função de espião da CIA, +no clássico "faço tudo pelo meu país", batendo no peito, mas mostra-se de +certa forma indignado quando comenta que outros países fazem o mesmo. O +clássico, "não confio em ninguém, mas fico indignado quando não confiam em +mim." -O segundo problema é a tradução: utiliza toda a língua formal no livro, com pedaços caindo para o popular: "a gente podia" ao invés de "nós poderíamos", "antes de se tornar um fera na maquiagem" ao invés de "antes de se tornar expert em maquiagem". Embora pareça bobo citar esses exemplos, eles são extremamente contrastantes com o resto da linguagem usada. +O segundo problema é a tradução: utiliza toda a língua formal no livro, com +pedaços caindo para o popular: "a gente podia" ao invés de "nós poderíamos", +"antes de se tornar um fera na maquiagem" ao invés de "antes de se tornar +expert em maquiagem". Embora pareça bobo citar esses exemplos, eles são +extremamente contrastantes com o resto da linguagem usada. -No fim, o livro é muito interessante pela explicação histórica dos eventos e para ver o quão disparate da verdade o filme é. \ No newline at end of file +No fim, o livro é muito interessante pela explicação histórica dos eventos e +para ver o quão disparate da verdade o filme é. diff --git a/content/reviews/books/arrival.md b/content/reviews/books/arrival.md index 6fdca12..e28e2df 100644 --- a/content/reviews/books/arrival.md +++ b/content/reviews/books/arrival.md @@ -2,17 +2,48 @@ title = "Arrival - Ted Chiang" date = 2017-02-28 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ted chiang"] +tags = ["books", "ted chiang", "reviews", "scifi", "fantasy"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/31625351-arrival): +From a soaring Babylonian tower that connects a flat Earth with the heavens +above, to a world where angelic visitations are a wondrous and terrifying part +of everyday life; from a neural modification that eliminates the appeal of +physical beauty, to an alien language that challenges our very perception of +time and reality... Chiang's rigorously imagined stories invite us to question +our understanding of the universe and our place in it. + + + + {{ stars(stars=5) }} -I'll be honest (again) and admit that I bought the book because of the movie (again -- the same thing happened with [book:All You Need Is Kill|6255949]/Edge of Tomorrow). This time, though, I haven't seen the movie yet, so I basically "read the movie" before watching it. +I'll be honest (again) and admit that I bought the book because of the movie +(again -- the same thing happened with [book:All You Need Is +Kill|6255949]/Edge of Tomorrow). This time, though, I haven't seen the movie +yet, so I basically "read the movie" before watching it. -Thing is, this is *not* just about Arrival. It's a collection of stories by Ted Chiang -- one of them is "The Story of Your Life", which is the base for the movie. You have "Tower of Babylon", which is kinda like a fantasy story if said tower actually reached the heavens; "Understand", which takes a stab in a "Limitless" kinda-way; "Division By Zero", which talks about mathematics but it is actually about people (Pro-tip: if you read, keep an eye on the "chapter" numbers; it will explain the story); "Story of Your Life", which, again, is the base for the Arrival movie; "Seventy-Two Letters", about a world where golems and controlling stuff with written stuff actually exists; "The Evolution About Human Science", a short story about a future when humans can't keep up with their own science; "Hell is the Absence of God", about angels (although the author explains it in the end, it felt much more like "this is hell" than anything else); and "Liking What You See: A Documentary", which feels like a huge discussion about beauty and propaganda. +Thing is, this is *not* just about Arrival. It's a collection of stories by +Ted Chiang -- one of them is "The Story of Your Life", which is the base for +the movie. You have "Tower of Babylon", which is kinda like a fantasy story if +said tower actually reached the heavens; "Understand", which takes a stab in a +"Limitless" kinda-way; "Division By Zero", which talks about mathematics but +it is actually about people (Pro-tip: if you read, keep an eye on the +"chapter" numbers; it will explain the story); "Story of Your Life", which, +again, is the base for the Arrival movie; "Seventy-Two Letters", about a world +where golems and controlling stuff with written stuff actually exists; "The +Evolution About Human Science", a short story about a future when humans can't +keep up with their own science; "Hell is the Absence of God", about angels +(although the author explains it in the end, it felt much more like "this is +hell" than anything else); and "Liking What You See: A Documentary", which +feels like a huge discussion about beauty and propaganda. -In general, all stories are pretty easy and interesting to read -- reading the whole book in two days may be a testament of this. The whole style reminded me of Asimov's writing, although I could skip half paragraphs without missing anything in the story, while that wouldn't be an option in Asimov stories. +In general, all stories are pretty easy and interesting to read -- reading the +whole book in two days may be a testament of this. The whole style reminded me +of Asimov's writing, although I could skip half paragraphs without missing +anything in the story, while that wouldn't be an option in Asimov stories. -The endings are also kinda loose, but because there are hidden clues about the story itself in other parts -- like in "Division By Zero" -- I guess I just didn't *get* them yet. \ No newline at end of file +The endings are also kinda loose, but because there are hidden clues about the +story itself in other parts -- like in "Division By Zero" -- I guess I just +didn't *get* them yet. diff --git a/content/reviews/books/backbonejs-essentials.md b/content/reviews/books/backbonejs-essentials.md index 0ba14d9..251b14e 100644 --- a/content/reviews/books/backbonejs-essentials.md +++ b/content/reviews/books/backbonejs-essentials.md @@ -2,15 +2,32 @@ title = "Backbone.js Essentials - Jeremy Walker" date = 2016-04-26 -category = "review" - [taxonomies] -tags = ["books", "en-au", "jeremy walker"] +tags = ["books", "jeremy walker", "backbone.js", "javascript", "reviews", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/25979896-backbone-js-essentials): +Construct top-notch web applications by mastering the powerful tools provided +by Backbone.js Gain insights into how to simplify data management and create +single-page web applications with powerful user interfaces This is a +fast-paced guide on how to test, document, and leverage third-party libraries, +and helps you get the most out of Backbone.js. + + + {{ stars(stars=3) }} -This is the second book about Backbone and, honestly, the more I read, the less I understand about it; but I believe that's absolutely only my fault. +This is the second book about Backbone and, honestly, the more I read, the +less I understand about it; but I believe that's absolutely only my fault. -Although the book explains each of the Backbone classes in deep, it never really connects one to another. It seriously lack a whole description on how to build an app from start to finish. Even if you know everything about collections and models (and that they represent a table and a record, respectively), how to create a View and how to route things around, you seriously lack the idea behind connecting one to another -- although Views are shown using Models directly, it should actually go on how to draw several models from a collection in a single step, for example. +Although the book explains each of the Backbone classes in deep, it never +really connects one to another. It seriously lack a whole description on how +to build an app from start to finish. Even if you know everything about +collections and models (and that they represent a table and a record, +respectively), how to create a View and how to route things around, you +seriously lack the idea behind connecting one to another -- although Views are +shown using Models directly, it should actually go on how to draw several +models from a collection in a single step, for example. -So, although good for understanding Backbone classes, it lacks on the general *building* of a Backbone app. \ No newline at end of file +So, although good for understanding Backbone classes, it lacks on the general +*building* of a Backbone app. diff --git a/content/reviews/books/backbonejs-testing.md b/content/reviews/books/backbonejs-testing.md index f5e5a79..2441b4e 100644 --- a/content/reviews/books/backbonejs-testing.md +++ b/content/reviews/books/backbonejs-testing.md @@ -2,15 +2,33 @@ title = "Backbone.Js Testing - Ryan Roemer" date = 2016-05-02 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ryan roemer"] +tags = ["books", "ryan roemer", "reviews", "backbone.js", "javascript", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18902858-backbone-js-testing): +This book is packed with the step by step tutorial and instructions in recipe +format helping you setup test infrastructure and gradually advance your skills +to plan, develop, and test your backbone applications.If you are a JavaScript +developer looking for recipes to create and implement test support for your +backbone application, then this book is ideal for you. + + + {{ stars(stars=5) }} -At the very begin of the book, the author mentioned that, for the sake of showing tests, there would be a complete application to be used as an example. My thought, at this point was: Finally, a book talking more about how to connect Backbone elements than _Backbone.js Essentials_. Well, I was mistaken. +At the very begin of the book, the author mentioned that, for the sake of +showing tests, there would be a complete application to be used as an example. +My thought, at this point was: Finally, a book talking more about how to +connect Backbone elements than _Backbone.js Essentials_. Well, I was mistaken. -There isn't much of Backbone itself in this book. When it says "Backbone.js *Testing*", it actually means that Backbone is just a background thingy to talk about Mocha, Chai and Sinon. If the author decided to write a "React.js Testing", there wouldn't be more much in the topics, just a few adjustments there and there. +There isn't much of Backbone itself in this book. When it says "Backbone.js +*Testing*", it actually means that Backbone is just a background thingy to +talk about Mocha, Chai and Sinon. If the author decided to write a "React.js +Testing", there wouldn't be more much in the topics, just a few adjustments +there and there. -This means this book is back? Actually not. Although not focusing directly on Backbone, it *does* focus a lot on testing and all related libraries. Even if you don't work with Backbone -- but have at least some general idea about how it works -- it is a damn good book about JavaScript testing. \ No newline at end of file +This means this book is back? Actually not. Although not focusing directly on +Backbone, it *does* focus a lot on testing and all related libraries. Even if +you don't work with Backbone -- but have at least some general idea about how +it works -- it is a damn good book about JavaScript testing. diff --git a/content/reviews/books/being-there.md b/content/reviews/books/being-there.md index e0abbe7..68aee5f 100644 --- a/content/reviews/books/being-there.md +++ b/content/reviews/books/being-there.md @@ -2,19 +2,42 @@ title = "Being There - Jerzy Kosiński" date = 2018-05-31 -category = "review" - [taxonomies] -tags = ["books", "en-au", "jerzy kosinski"] +tags = ["books", "jerzy kosinski", "reviews", "fiction"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/677877.Being_There): +A modern classic now available from Grove Press, Being There is one of the +most popular and significant works from a writer of international stature. It +is the story of Chauncey Gardiner - Chance, an enigmatic but distinguished man +who emerges from nowhere to become an heir to the throne of a Wall Street +tycoon, a presidential policy adviser, and a media icon. Truly "a man without +qualities," Chance's straightforward responses to popular concerns are +heralded as visionary. But though everyone is quoting him, no one is sure what +he's really saying. And filling in the blanks in his background proves +impossible. Being There is a brilliantly satiric look at the unreality of +American media culture that is, if anything, more trenchant now than ever. + + + {{ stars(stars=2) }} -It's a somewhat funny story. It's also short. But I can't stop thinking "What the heck I just read?" +It's a somewhat funny story. It's also short. But I can't stop thinking "What +the heck I just read?" -I've seen a lot about the movie (with the same name) but I've never seen the movie itself. So I read the book. +I've seen a lot about the movie (with the same name) but I've never seen the +movie itself. So I read the book. -But the story... I don't know if Kosinski just wanted to write something funny or was trying to make a statement about the higher classes. 'Cause Chance is dumb as a brick, but after being hit by a car of a high society socialite, suddenly he's elevated to the point of being the smartest, most desired person around. +But the story... I don't know if Kosinski just wanted to write something funny +or was trying to make a statement about the higher classes. 'Cause Chance is +dumb as a brick, but after being hit by a car of a high society socialite, +suddenly he's elevated to the point of being the smartest, most desired person +around. -So you see the kind of comic situations you could do with this. But also, because everything sees him as a super smart persona, you can't stop thinking that, maybe, Kosinski wanted to point how being rich isn't synonymous of "being intelligent". +So you see the kind of comic situations you could do with this. But also, +because everything sees him as a super smart persona, you can't stop thinking +that, maybe, Kosinski wanted to point how being rich isn't synonymous of +"being intelligent". -And, because you never know where the author is pointing at the the story ends rather abruptly, I can't really say it's a good story. \ No newline at end of file +And, because you never know where the author is pointing at the the story ends +rather abruptly, I can't really say it's a good story. diff --git a/content/reviews/books/black-hat-python-python-programming-for-hackers-and-pentesters.md b/content/reviews/books/black-hat-python-python-programming-for-hackers-and-pentesters.md index 38372ae..6102472 100644 --- a/content/reviews/books/black-hat-python-python-programming-for-hackers-and-pentesters.md +++ b/content/reviews/books/black-hat-python-python-programming-for-hackers-and-pentesters.md @@ -2,21 +2,49 @@ title = "Black Hat Python: Python Programming for Hackers and Pentesters - Justin Seitz" date = 2016-12-26 -category = "review" - [taxonomies] -tags = ["books", "en-au", "justin seitz"] +tags = ["books", "justin seitz", "python", "pentest", "reviews", "it"] +++ -{{ stars(stars=2) }} -The very first chapter give me high hopes for this book: Since Python is basically part of every single Linux install, you could do a shitton retrieving system and user information by just using the normal packages. You won't even need to install nmap or similar; using plain Python packages, you could check which services are running and such. +[GoodReads Summary](https://www.goodreads.com/book/show/22299369-black-hat-python): +When it comes to creating powerful and effective hacking tools, Python is the +language of choice for most security analysts. But just how does the magic +happen? -But then, things go downhill. + -After the first chapter, you start to add Python packages, which means you need to have root access -- and even if you use something like a virtualenv, you still would announce yourself by requesting things over the net using easy_install (the book never mentions pip -- heck, it doesn't even *mentions* virtualenv to avoid being root), which could be easily blocked by sysadmins if your company doesn't have anything with Python. +{{ stars(stars=2) }} -And it doesn't stop at that: after these starting chapters, it start hacking Windows machines. Heck, Python is not installed by default on Windows and a py2exe executable weights something like 15Mb, which isn't much in bandwidth, but it's noticeable. And then it starts installing packages and more packages and requesting to run things as administrator, which would surely be a hassle. +The very first chapter give me high hopes for this book: Since Python is +basically part of every single Linux install, you could do a shitton +retrieving system and user information by just using the normal packages. You +won't even need to install nmap or similar; using plain Python packages, you +could check which services are running and such. -The Python code itself is simplistic, to say the least. At the very first chapters I noticed that the code was basically C code translated to Python, which wouldn't be a problem if you're thinking about replacing basic hack code with Python code -- because it is easier to find Python installed than GCC, for example -- but with the problems cited above actually make me think that the author never really cared about Pythonic code, just did the very minimum to make code run and that's it. +But then, things go downhill. -So, it's a bad book about hacking because it requires privileged access beforehand and it's a bad book about Python because it doesn't follow Python good practices. In the end, it's just a book with a few interesting Python libraries, nothing more. \ No newline at end of file +After the first chapter, you start to add Python packages, which means you +need to have root access -- and even if you use something like a virtualenv, +you still would announce yourself by requesting things over the net using +easy_install (the book never mentions pip -- heck, +it doesn't even *mentions* virtualenv to avoid being root), which could be +easily blocked by sysadmins if your company doesn't have anything with Python. + +And it doesn't stop at that: after these starting chapters, it start hacking +Windows machines. Heck, Python is not installed by default on Windows and a +py2exe executable weights something like 15Mb, which isn't much in bandwidth, +but it's noticeable. And then it starts installing packages and more packages +and requesting to run things as administrator, which would surely be a hassle. + +The Python code itself is simplistic, to say the least. At the very first +chapters I noticed that the code was basically C code translated to Python, +which wouldn't be a problem if you're thinking about replacing basic hack code +with Python code -- because it is easier to find Python installed than GCC, +for example -- but with the problems cited above actually make me think that +the author never really cared about Pythonic code, just did the very minimum +to make code run and that's it. + +So, it's a bad book about hacking because it requires privileged access +beforehand and it's a bad book about Python because it doesn't follow Python +good practices. In the end, it's just a book with a few interesting Python +libraries, nothing more. diff --git a/content/reviews/books/brave-new-world.md b/content/reviews/books/brave-new-world.md index bc0630b..e9c21a3 100644 --- a/content/reviews/books/brave-new-world.md +++ b/content/reviews/books/brave-new-world.md @@ -2,21 +2,47 @@ title = "Brave New World - Aldous Huxley" date = 2014-12-31 -category = "review" - [taxonomies] -tags = ["books", "en-au", "aldous huxley"] +tags = ["books", "aldous huxley", "reviews", "scifi", "fantasy"] +++ -{{ stars(stars=3) }} - -There is a weird thing about "Brave New World". Well, there are a bunch of weird things, like the pacing, the idea in the early chapters which make it confusing to see where the author wants to go but, on top of that, there is this dystopian future (apparently, 300 or 400 years from the early 20th century) that sounds so much like our days. -The book opens with a very dystopian society: People are bred, not born, and the needs of the society decide the type of people who will be born: Do we need more administrators? Then we'll have this kind of people; do we need more workers? Then we'll have a bunch of twins with low IQ that will be prepared to do menial tasks. +[GoodReads Summary](https://www.goodreads.com/book/show/5129.Brave_New_World): +Brave New World is a dystopian novel by English author Aldous Huxley, written in 1931 and published in 1932. Largely set in a futuristic World State, inhabited by genetically modified citizens and an intelligence-based social hierarchy, the novel anticipates huge scientific advancements in reproductive technology, sleep-learning, psychological manipulation and classical conditioning that are combined to make a dystopian society which is challenged by only a single individual: the story's protagonist. -Not only that, but people are thought, at the very age, by continuous reinforcement propaganda that things like "marriage", "naturally born", "father", "mother" and other things are actually bad; we need more money being spent in the country, so let's train people to like being outside the cities; clothing is thrown away because that makes the clothing industry prosper (instead of simply mending); people are actually encouraged to be promiscuous (sorta) in other to never feel lonely. + -(In part, this resonates a bit with _The Robots of Dawn_, but while in Aurora people would engage sex when they felt like, in Brave New World people engage sex because they are massively pressured since their early training to do so.) - -But then again there are small pockets of people who are not part of the *society*, being kept in *Savage Reservations*. And when one of such "savages" is brought back into *society*, then we have our discussion about total free will and the workings of a completely conditioned and "harmonic" (with quotes) society. +{{ stars(stars=3) }} -Again, it's weird to understand where the author wants to go in the early chapters, but the final chapters (with the exception of the end of the last one) are pretty damn thought provoking. \ No newline at end of file +There is a weird thing about "Brave New World". Well, there are a bunch of +weird things, like the pacing, the idea in the early chapters which make it +confusing to see where the author wants to go but, on top of that, there is +this dystopian future (apparently, 300 or 400 years from the early 20th +century) that sounds so much like our days. + +The book opens with a very dystopian society: People are bred, not born, and +the needs of the society decide the type of people who will be born: Do we +need more administrators? Then we'll have this kind of people; do we need more +workers? Then we'll have a bunch of twins with low IQ that will be prepared to +do menial tasks. + +Not only that, but people are thought, at the very age, by continuous +reinforcement propaganda that things like "marriage", "naturally born", +"father", "mother" and other things are actually bad; we need more money being +spent in the country, so let's train people to like being outside the cities; +clothing is thrown away because that makes the clothing industry prosper +(instead of simply mending); people are actually encouraged to be promiscuous +(sorta) in other to never feel lonely. + +(In part, this resonates a bit with _The Robots of Dawn_, but while in Aurora +people would engage sex when they felt like, in Brave New World people engage +sex because they are massively pressured since their early training to do so.) + +But then again there are small pockets of people who are not part of the +*society*, being kept in *Savage Reservations*. And when one of such "savages" +is brought back into *society*, then we have our discussion about total free +will and the workings of a completely conditioned and "harmonic" (with quotes) +society. + +Again, it's weird to understand where the author wants to go in the early +chapters, but the final chapters (with the exception of the end of the last +one) are pretty damn thought provoking. diff --git a/content/reviews/books/c-succinctly.md b/content/reviews/books/c-succinctly.md index 110dbb2..ffb7d0f 100644 --- a/content/reviews/books/c-succinctly.md +++ b/content/reviews/books/c-succinctly.md @@ -2,13 +2,21 @@ title = "C# Succinctly - Joe Mayo" date = 2016-04-17 -category = "review" - [taxonomies] -tags = ["books", "en-au", "joe mayo"] +tags = ["books", "joe mayo", "reviews", "it", "c#"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/26101445-c-succinctly): +(No summary.) + + + {{ stars(stars=2) }} -I know that "succinctly"doesn't mean "let's explore everything", but there are some things that really need some better explanations. +I know that "succinctly" doesn't mean "let's explore everything", but there are +some things that really need some better explanations. -First of all, this is not a book for starters. If you never coded in your live, getting the basics will be really hard. Second, there are some things that, because you already coded, look a bit weird in the way that either C# is a magical language or there is something really wrong with the code. \ No newline at end of file +First of all, this is not a book for starters. If you never coded in your +live, getting the basics will be really hard. Second, there are some things +that, because you already coded, look a bit weird in the way that either C# is +a magical language or there is something really wrong with the code. diff --git a/content/reviews/books/changing-planes-stories.md b/content/reviews/books/changing-planes-stories.md index 80108a6..3a1a60d 100644 --- a/content/reviews/books/changing-planes-stories.md +++ b/content/reviews/books/changing-planes-stories.md @@ -2,15 +2,30 @@ title = "Changing Planes: Stories - Ursula K. Le Guin" date = 2018-03-13 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ursula k. le guin"] +tags = ["books", "ursula k. le guin", "reviews", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/13657.Changing_Planes): +Sita Dulip has missed her flight. But instead of listening to garbled +announcements in the airport, she has found a method of bypassing the crowds +at the desks, the long lines at the toilets, the nasty lunch, the whimpering +children and punitive parents, the bookless bookstores, and the blue plastic +chairs bolted to the floor. + + + {{ stars(stars=4) }} -This was the first book of Ursula that I've read, even if I'm used to read Scifi from Asimov, Clark and Heinlein. But Ursula is a complete different style from those. +This was the first book of Ursula that I've read, even if I'm used to read +Scifi from Asimov, Clark and Heinlein. But Ursula is a complete different +style from those. -"Changing Planes" can be described as "she took her dreams and turned into stories". It's a story of several "planes" of existence, each with its own history, its own culture and its own people. Each is different from the other in almost non-overlapping fashion. +"Changing Planes" can be described as "she took her dreams and turned into +stories". It's a story of several "planes" of existence, each with its own +history, its own culture and its own people. Each is different from the other +in almost non-overlapping fashion. -At first it's kinda weird and uninteresting -- till you realize how much creativity one has to have to come up with several different different planets and their history. \ No newline at end of file +At first it's kinda weird and uninteresting -- till you realize how much +creativity one has to have to come up with several different different planets +and their history. diff --git a/content/reviews/books/chthon.md b/content/reviews/books/chthon.md index a94fb5f..85588db 100644 --- a/content/reviews/books/chthon.md +++ b/content/reviews/books/chthon.md @@ -3,7 +3,7 @@ title = "Chthon - Piers Anthony" date = 2019-09-13 [taxonomies] -tags = ["books", "reviews", "en-au", "piers anthony", "scifi"] +tags = ["books", "reviews", "piers anthony", "scifi"] +++ [Goodreads Summary](https://www.goodreads.com/book/show/23352267-chthon): diff --git a/content/reviews/books/clean-code-a-handbook-of-agile-software-craftsmanship.md b/content/reviews/books/clean-code-a-handbook-of-agile-software-craftsmanship.md index f0aec97..c0b61a2 100644 --- a/content/reviews/books/clean-code-a-handbook-of-agile-software-craftsmanship.md +++ b/content/reviews/books/clean-code-a-handbook-of-agile-software-craftsmanship.md @@ -2,25 +2,53 @@ title = "Clean Code: A Handbook of Agile Software Craftsmanship - Robert C. Martin" date = 2015-01-25 -category = "review" - [taxonomies] -tags = ["books", "en-au", "robert c. martin"] +tags = ["books", "robert c. martin", "it", "reviews"] +++ -{{ stars(stars=3) }} - -About the edition - -If there is one single weird thing about the Kindle edition is the code formatting. While reading code in non-monospaced font is weird but not impossible, reading code in non-monospaced font that is justified like normal text is. -The really annoying part is that, at the end of the book, the full listing of the discussed code is shown as "images", large blocks of code that don't follow the selected Kindle background and doesn't seem to allow selection, but it is monospaced and it is not justified. Why won't they use it all over the code is beyond me. +[GoodReads Summary](https://www.goodreads.com/book/show/3735293-clean-code): +Even bad code can function. But if code isn t clean, it can bring a +development organization to its knees. Every year, countless hours and +significant resources are lost because of poorly written code. But it doesn t +have to be that way. -About the content + -The book goes with a good start, listing almost all the pet peeves I have with other people code ("why the fuck they named things like this?", "why the hell this function have that many parameters?" and so on -- heck, even the problem with consistent style was there). Although it points the problem and how to improved it, it sometimes lacks the why those changes need to be made. - -But, then, things start to really go downhill, with lots of stuff that contradicts previous statements (specially the Single Responsibility Principle), and a bunch of things that are language specific. There is one really good chapter that picks a code and goes slowly showing the principles discussed in the start of the book, applying one after the other, so you can see the code changing and becoming easier to read. The sad part is that it is used only once. - -Honestly, I which there was a lot more of "why you should do this", only because as a seasoned programmer, I agree -- and use -- with a lot of the points in the book, but I lack the experience the tell younger programmers why they should not do what they are doing. +{{ stars(stars=3) }} -It's a good book, nonetheless, although not exceptionally good. \ No newline at end of file +**About the edition** + +If there is one single weird thing about the Kindle edition is the code +formatting. While reading code in non-monospaced font is weird but not +impossible, reading code in non-monospaced font that is justified like normal +text _is_. + +The really annoying part is that, at the end of the book, the full listing of +the discussed code is shown as "images", large blocks of code that don't +follow the selected Kindle background and doesn't seem to allow selection, but +it _is_ monospaced and it is _not_ justified. Why won't they use +it all over the code is beyond me. + +**About the content** + +The book goes with a good start, listing almost all the pet peeves I have with +other people code ("why the _fuck_ they named things like +_this_?", "why the _hell_ this function have that many +parameters?" and so on -- heck, even the problem with consistent style was +there). Although it points the problem and how to improved it, it sometimes +lacks the _why_ those changes need to be made. + +But, then, things start to really go downhill, with lots of stuff that +contradicts previous statements (specially the Single Responsibility +Principle), and a bunch of things that are language specific. There is one +really good chapter that picks a code and goes slowly showing the principles +discussed in the start of the book, applying one after the other, so you can +see the code changing and becoming easier to read. The sad part is that it is +used only once. + +Honestly, I which there was a lot more of "why you should do this", only +because as a seasoned programmer, I agree -- and use -- with a lot of the +points in the book, but I lack the experience the tell younger programmers +_why_ they should not do what they are doing. + +It's a good book, nonetheless, although not exceptionally good. diff --git a/content/reviews/books/clojure-for-machine-learning.md b/content/reviews/books/clojure-for-machine-learning.md index a054a59..63e65c6 100644 --- a/content/reviews/books/clojure-for-machine-learning.md +++ b/content/reviews/books/clojure-for-machine-learning.md @@ -2,19 +2,40 @@ title = "Clojure for Machine Learning - Akhil Wali" date = 2017-05-01 -category = "review" - [taxonomies] -tags = ["books", "en-au", "akhil wali"] +tags = ["books", "akhil wali", "reviews", "clojure", "it", "machine learning"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/22062479-clojure-for-machine-learning): +Clojure for Machine Learning is an introduction to machine learning techniques +and algorithms. This book demonstrates how you can apply these techniques to +real-world problems using the Clojure programming language. + +It explores many machine learning techniques and also describes how to use +Clojure to build machine learning systems. This book starts off by introducing +the simple machine learning problems of regression and classification. It also +describes how you can implement these machine learning techniques in Clojure. +The book also demonstrates several Clojure libraries, which can be useful in +solving machine learning problems. + + + {{ stars(stars=2) }} If I ever read a book with a misleading title, that would be it. -Not because there is no Clojure in it, but the amount of Clojure used is minimal compared to the whole. +Not because there is no Clojure in it, but the amount of Clojure used is +minimal compared to the whole. -Also, not because there is no Machine Learning in it, but the book goes as deep as explaining the algorithms behind each common machine learning technique, without explaining *when* you should use it. There is ample discussion about the mathematical context of each method, but it explains absolutely nothing about machine learning itself -- it's purely a bunch of mathematical equations that could be use to extract some pattern, but it's hardly "machine learning" at this point. +Also, not because there is no Machine Learning in it, but the book goes as +deep as explaining the algorithms behind each common machine learning +technique, without explaining *when* you should use it. There is ample +discussion about the mathematical context of each method, but it explains +absolutely nothing about machine learning itself -- it's purely a bunch of +mathematical equations that could be use to extract some pattern, but it's +hardly "machine learning" at this point. (Also: Neural networks as "unsupervised learning"?!?) -So, good book on the math behind some machine learning equations, very bad clojure, very bad machine learning. \ No newline at end of file +So, good book on the math behind some machine learning equations, very bad +clojure, very bad machine learning. diff --git a/content/reviews/books/clojure-for-the-brave-and-true.md b/content/reviews/books/clojure-for-the-brave-and-true.md index 5b1ccb9..9b6ea2f 100644 --- a/content/reviews/books/clojure-for-the-brave-and-true.md +++ b/content/reviews/books/clojure-for-the-brave-and-true.md @@ -2,17 +2,47 @@ title = "Clojure for the Brave and True - Daniel Higginbotham" date = 2017-04-09 -category = "review" - [taxonomies] -tags = ["books", "en-au", "daniel higginbotham"] +tags = ["books", "daniel higginbotham", "clojure", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/20873338-clojure-for-the-brave-and-true): +As a Lisp-style functional programming language, Clojure lets you write robust +and elegant code, and because it runs on the Java Virtual Machine, you can +take advantage of the vast Java ecosystem. Clojure for the Brave and True +offers a "dessert-first" approach: you'll start playing with real programs +immediately, as you steadily acclimate to the abstract but powerful features +of Lisp and functional programming. Inside you'll find an offbeat, practical +guide to Clojure, filled with quirky sample programs that catch cheese thieves +and track glittery vampires. + + + {{ stars(stars=3) }} -There must be something wrong with Lisp (and Lisp-like) people that when they write about their language, they show the code first, then explain what they wrote -- which is kinda weird, because you read code that you barely understand what it is doing at first, then they explain and you have to go back and read it again to finally "click" it. And, sometimes, they forget what code they just wrote and you're left with commands that you have no idea what they do. +There must be something wrong with Lisp (and Lisp-like) people that when they +write about their language, they show the code first, then explain what they +wrote -- which is kinda weird, because you read code that you barely +understand what it is doing at first, then they explain and you have to go +back and read it again to finally "click" it. And, sometimes, they forget what +code they just wrote and you're left with commands that you have no idea what +they do. -There is also a weird sense of humor, which I believe it could be fun if you watch whatever TV series the author uses as reference. For someone that doesn't follow and doesn't know what he's talking about, it's just... weird -- and not fun at all. Fortunately, the "humor" tones down to the end, which makes more "pleasant" to read. +There is also a weird sense of humor, which I believe it could be fun if you +watch whatever TV series the author uses as reference. For someone that +doesn't follow and doesn't know what he's talking about, it's just... weird -- +and not fun at all. Fortunately, the "humor" tones down to the end, which +makes more "pleasant" to read. -While it covers a lot of ground in the book, some pieces really fall short in their examples. Threading and process fall short due the use of sleep, which is not something you'd normally write; the last appendix, about a tool called "Boot" tries to explain some concepts about tasks and middlewares with things that are not tasks and do not reflect the real world. Lacking this connection to real use of a tool just make things harder to udnerstand -- and even harder to see *where* you'd use it. +While it covers a lot of ground in the book, some pieces really fall short in +their examples. Threading and process fall short due the use of +sleep, which is not something you'd normally write; the last +appendix, about a tool called "Boot" tries to explain some concepts about +tasks and middlewares with things that are not tasks and do not reflect the +real world. Lacking this connection to real use of a tool just make things +harder to udnerstand -- and even harder to see *where* you'd use it. -It's not the worst book about a Lisp-like language I've read -- and heck, it does a good job *selling* the language, to the point I'm already thinking about writing something in it -- but damn if these problems don't appear in every single one of those. \ No newline at end of file +It's not the worst book about a Lisp-like language I've read -- and heck, it +does a good job *selling* the language, to the point I'm already thinking +about writing something in it -- but damn if these problems don't appear in +every single one of those. diff --git a/content/reviews/books/coffeescript-application-development.md b/content/reviews/books/coffeescript-application-development.md index f356f16..2833c3e 100644 --- a/content/reviews/books/coffeescript-application-development.md +++ b/content/reviews/books/coffeescript-application-development.md @@ -2,15 +2,51 @@ title = "CoffeeScript Application Development - Ian Young" date = 2016-05-07 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ian young"] +tags = ["books", "ian young", "reviews", "javascript", "coffeescript", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18430540-coffeescript-application-development): +What JavaScript user wouldnt want to be able to dramatically reduce +application development time This book will teach you the clean, elegant +CoffeeScript language and show you how to build stunning applications. +Overview Learn the ins and outs of the CoffeeScript language, and understand +how the transformation happens behind the scenes Use practical examples to put +your new skills to work towards building a functional web application, written +entirely in CoffeeScript Understand the language concepts from short, +easy-to-understand examples which can be practised by applying them to your +ongoing project In Detail JavaScript is becoming one of the key languages in +web development. It is now more important than ever across a growing list of +platforms. CoffeeScript puts the fun back into JavaScript programming with +elegant syntax and powerful features. CoffeeScript Application Development +will give you an in-depth look at the CoffeeScript language, all while +building a working web application. Along the way, youll see all the great +features CoffeeScript has to offer, and learn how to use them to deal with +real problems like sprawling codebases, incomplete data, and asynchronous web +requests. Through the course of this book you will learn the CoffeeScript +syntax and see it demonstrated with simple examples. As you go, youll put your +new skills into practice by building a web application, piece by piece. Youll +start with standard language features such as loops, functions, and string +manipulation. Then, well delve into advanced features like classes and +inheritance. Learn advanced idioms to deal with common occurrences like +external web requests, and hone your technique for development tasks like +debugging and refactoring. CoffeeScript Application Development will teach you +not only how to write CoffeeScript, but also how to build solid applications +that run smoothly and are a pleasure to maintain. + + + + {{ stars(stars=4) }} -In these days of ECMAScript 6, it's nice to see where a bunch of ideas of it came from. +In these days of ECMAScript 6, it's nice to see where a bunch of ideas of it +came from. -Coffee is a lot like the new JavaScript standard (just a bit more brackets). The book manages to explain and show all the little nice things about it, keeping a single application from start to finish, which helps a lot in understanding the flows of it. +Coffee is a lot like the new JavaScript standard (just a bit more brackets). +The book manages to explain and show all the little nice things about it, +keeping a single application from start to finish, which helps a lot in +understanding the flows of it. -I just got a bit miffed with the upbeat tone of the book. It's not a full Pollyanna, but a lot of "that looks a lot cleaner, don't it?" and "It's even prettier than normal Javascript" gets into you pretty quick. \ No newline at end of file +I just got a bit miffed with the upbeat tone of the book. It's not a full +Pollyanna, but a lot of "that looks a lot cleaner, don't it?" and "It's even +prettier than normal Javascript" gets into you pretty quick. diff --git a/content/reviews/books/como-a-musica-ficou-gratis.md b/content/reviews/books/como-a-musica-ficou-gratis.md index 33c6e58..29ed9d1 100644 --- a/content/reviews/books/como-a-musica-ficou-gratis.md +++ b/content/reviews/books/como-a-musica-ficou-gratis.md @@ -2,21 +2,54 @@ title = "Como a música ficou grátis - Stephen Witt" date = 2016-05-21 -category = "review" - [taxonomies] -tags = ["books", "en-au", "stephen witt"] +tags = ["books", "pt-br", "stephen witt", "review", "streaming", "música"] +++ -{{ stars(stars=4) }} - -“Como a música ficou grátis” é uma análise dos fatos que aconteceram com a indústria fonográfica acabou dando vários tiros nos pés até que músicas fossem gratuitamente distribuidas pela internet. -E não, não estamos falando sobre as “rádios online” que hoje estão em todos os lugares. O livro acaba antes dessa explosão, mas a história contada deixa relativamente explicado do porque essa explosão aconteceu, se você conseguir ligar as linhas. +[Resumo GoodReads](https://www.goodreads.com/book/show/31306379-como-a-m-sica-ficou-gr-tis): +Uma trama impressionante envolvendo música, crime, dinheiro e obsessão, cujos +protagonistas são magnatas, pesquisadores respeitados, criminosos e +adolescentes nerds fissurados em tecnologia. -O livro se foca na história de três pessoas (principalmente): Doug Morris, produtor musical que descobriu vários artistas de ponta, principalmente no mundo do rap; Karlheinz Brandenburg, do Instituto de Erlagen-Nuremberg, que trabalhou no formato hoje conhecido como MP3; e, finalmente, Dell Glover, que trabalhou numa das fábricas de prensagens de CDs da Universal Music e conseguiu vazar vários álbuns antes dos seus lançamentos oficiais. + -Embora o livro conte, de forma bem explícita, como a vida dessas três pessoas influenciou uma indústria inteira, eu fiquei com a impressão que acontecimentos realmente importantes nessa história tenham ficado de lado. Por exemplo, a explosão do Napster é contada rapidamente, pulando da sua criação diretamente para o fechamento da empresa (os criadores do Napster, Shawn Fanning, John Fanning e Sean Parker são mencionados de relance, apenas); o lançamento do iPod também é colocado em segundo plano, apesar de ter sido o expoente máximo do MP3 na época apresentada pelo livro; BitTorrent aparece, mas apenas como um novo formato de distribuição para substituir o Napster; o Oink’s Pink Palace ganha mais proeminencia que o Pirate Bay; e, como dito inicialmente, a explosão das “rádios de internet” sequer é mencionada (ok, fala-se rapidamente do Spotify, mas é isso). - -Pode ser que o ponto do livro fosse, realmente, apresentar os fatores que não foram apresentados ao público, deixando os fatos mais “populares” de fora e apresentando o que estava acontecendo por baixo dos panos. Mas ainda assim, é estranho que coisas com relativa importância no contexto global da ação tenham sido sumariamente ignorados. +{{ stars(stars=4) }} -Outro problema com o livro é a leitura. Por algum motivo, o conteúdo é complicado de ser lido, possivelmente porque vai construindo hipótese sobre hipótese e contexto sobre contexto, o que deixa o livro “lento” de ser lido. \ No newline at end of file +“Como a música ficou grátis” é uma análise dos fatos que aconteceram com a +indústria fonográfica acabou dando vários tiros nos pés até que músicas fossem +gratuitamente distribuidas pela internet. + +E não, não estamos falando sobre as “rádios online” que hoje estão em todos os +lugares. O livro acaba antes dessa explosão, mas a história contada deixa +relativamente explicado do porque essa explosão aconteceu, se você conseguir +ligar as linhas. + +O livro se foca na história de três pessoas (principalmente): Doug Morris, +produtor musical que descobriu vários artistas de ponta, principalmente no +mundo do rap; Karlheinz Brandenburg, do Instituto de Erlagen-Nuremberg, que +trabalhou no formato hoje conhecido como MP3; e, finalmente, Dell Glover, que +trabalhou numa das fábricas de prensagens de CDs da Universal Music e +conseguiu vazar vários álbuns antes dos seus lançamentos oficiais. + +Embora o livro conte, de forma bem explícita, como a vida dessas três pessoas +influenciou uma indústria inteira, eu fiquei com a impressão que +acontecimentos realmente importantes nessa história tenham ficado de lado. Por +exemplo, a explosão do Napster é contada rapidamente, pulando da sua criação +diretamente para o fechamento da empresa (os criadores do Napster, Shawn +Fanning, John Fanning e Sean Parker são mencionados de relance, apenas); o +lançamento do iPod também é colocado em segundo plano, apesar de ter sido o +expoente máximo do MP3 na época apresentada pelo livro; BitTorrent aparece, +mas apenas como um novo formato de distribuição para substituir o Napster; o +Oink’s Pink Palace ganha mais proeminencia que o Pirate Bay; e, como dito +inicialmente, a explosão das “rádios de internet” sequer é mencionada (ok, +fala-se rapidamente do Spotify, mas é isso). + +Pode ser que o ponto do livro fosse, realmente, apresentar os fatores que não +foram apresentados ao público, deixando os fatos mais “populares” de fora e +apresentando o que estava acontecendo por baixo dos panos. Mas ainda assim, é +estranho que coisas com relativa importância no contexto global da ação tenham +sido sumariamente ignorados. + +Outro problema com o livro é a leitura. Por algum motivo, o conteúdo é +complicado de ser lido, possivelmente porque vai construindo hipótese sobre +hipótese e contexto sobre contexto, o que deixa o livro “lento” de ser lido. diff --git a/content/reviews/books/como-convencer-alguem-em-90-segundos.md b/content/reviews/books/como-convencer-alguem-em-90-segundos.md index d9f10d1..22e85eb 100644 --- a/content/reviews/books/como-convencer-alguem-em-90-segundos.md +++ b/content/reviews/books/como-convencer-alguem-em-90-segundos.md @@ -2,13 +2,29 @@ title = "Como convencer alguém em 90 segundos - Nicholas Boothman" date = 2016-07-24 -category = "review" - [taxonomies] -tags = ["books", "en-au", "nicholas boothman"] +tags = ["books", "pt-br", "nicholas boothman", "reviews"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/31222406-como-convencer-algu-m-em-90-segundos): +Como convencer alguém em 90 segundos é a garantia de uma comunicação de +sucesso, transformando as conexões instantâneas em duradouras e produtivas +relações de negócios. Neste livro, o especialista Nicholas Boothman ensina +como usar o rosto, o corpo, a atitude e a voz para causar uma primeira +impressão marcante, estabelecendo confiança imediata e criando fortes vínculos +de credibilidade. + + + {{ stars(stars=4) }} -Antes de mais nada, esse livro não é um livro de persuasão, de fazer outras pessoas terem a mesma convicção que você; esse livro é como convencer alguém a comprar algo de você -- seja produto ou seja você mesmo. +Antes de mais nada, esse livro não é um livro de persuasão, de fazer outras +pessoas terem a mesma convicção que você; esse livro é como convencer alguém a +comprar algo de você -- seja produto ou seja você mesmo. -Existem vários "exercícios" para conseguir aprender as regras de convencer alguém: como olhar alguém nos olhos, como estar sempre sorrindo, como contar uma história que capture a atenção das pessoas.... cada ponto tem um exercício. Além disso, no final de cada capítulo, existe um resumo do que foi falado no livro -- embora a forma como esse resumo apareça não tenha nenhum indicativo que é o resumo e não apenas mais um tópico do capítulo. \ No newline at end of file +Existem vários "exercícios" para conseguir aprender as regras de convencer +alguém: como olhar alguém nos olhos, como estar sempre sorrindo, como contar +uma história que capture a atenção das pessoas.... cada ponto tem um +exercício. Além disso, no final de cada capítulo, existe um resumo do que foi +falado no livro -- embora a forma como esse resumo apareça não tenha nenhum +indicativo que é o resumo e não apenas mais um tópico do capítulo. diff --git a/content/reviews/books/designing-data-intensive-applications-the-big-ideas-behind-reliable-scalable-and-maintainable-systems.md b/content/reviews/books/designing-data-intensive-applications-the-big-ideas-behind-reliable-scalable-and-maintainable-systems.md index 18073ee..1398f8d 100644 --- a/content/reviews/books/designing-data-intensive-applications-the-big-ideas-behind-reliable-scalable-and-maintainable-systems.md +++ b/content/reviews/books/designing-data-intensive-applications-the-big-ideas-behind-reliable-scalable-and-maintainable-systems.md @@ -2,19 +2,51 @@ title = "Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems - Martin Kleppmann" date = 2018-01-19 -category = "review" - [taxonomies] -tags = ["books", "en-au", "martin kleppmann"] +tags = ["books", "martin kleppmann", "reviews", "it", "big data"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/34626431-designing-data-intensive-applications): +Data is at the center of many challenges in system design today. Difficult +issues need to be figured out, such as scalability, consistency, reliability, +efficiency, and maintainability. In addition, we have an overwhelming variety +of tools, including relational databases, NoSQL datastores, stream or batch +processors, and message brokers. What are the right choices for your +application? How do you make sense of all these buzzwords? + +In this practical and comprehensive guide, author Martin Kleppmann helps you +navigate this diverse landscape by examining the pros and cons of various +technologies for processing and storing data. Software keeps changing, but the +fundamental principles remain the same. With this book, software engineers and +architects will learn how to apply those ideas in practice, and how to make +full use of data in modern applications. + + + {{ stars(stars=3) }} -First off, right out of the bat: If you want to design Data Intensive Applications, this is *not* the book you're looking for. This book goes greats lengths to explain how already existing Data Intensive Applications work -- say, how Zookeeper works when synching data, how Cassandra works without a leader, how PostgreSQL do transactions and so on. +First off, right out of the bat: If you want to design Data Intensive +Applications, this is *not* the book you're looking for. This book goes greats +lengths to explain how already existing Data Intensive Applications work -- +say, how Zookeeper works when synching data, how Cassandra works without a +leader, how PostgreSQL do transactions and so on. -While informative, the biggest problem is that most of the text is very loaded: there are layers and layers on each paragraph and you'll take a long time putting it all together. +While informative, the biggest problem is that most of the text is very +loaded: there are layers and layers on each paragraph and you'll take a long +time putting it all together. -Personaly, I felt it lacked examples. Sure, it's interesting how many ways you can do leader election, but which databases use this or that way? I can see that one way is the way I want to build my applications on top, but without a really good example, where should I look? +Personaly, I felt it lacked examples. Sure, it's interesting how many ways you +can do leader election, but which databases use this or that way? I can see +that one way is the way I want to build my applications on top, but without a +really good example, where should I look? -Also, there is a slight tendency to describe the "market winners" in way more detail than everything else. There are long discussions about the ways Cassandra solves its problems than Voldermort (obviously, there is a reason why Cassandra is the market winner, but this "over-focus" on certain applications is tiring and just do a job on keeping those on top -- because that's the ones the book talks and who will look at a database called Voldermort when you mention it just in passing?) +Also, there is a slight tendency to describe the "market winners" in way more +detail than everything else. There are long discussions about the ways +Cassandra solves its problems than Voldermort (obviously, there is a reason +why Cassandra is the market winner, but this "over-focus" on certain +applications is tiring and just do a job on keeping those on top -- because +that's the ones the book talks and who will look at a database called +Voldermort when you mention it just in passing?) -Overall, it felt like reading my old "Operating Systems 101" books again -- in a theorical way, not productive way. \ No newline at end of file +Overall, it felt like reading my old "Operating Systems 101" books again -- in +a theorical way, not productive way. diff --git a/content/reviews/books/direto-ao-ponto-criando-produtos-de-forma-enxuta.md b/content/reviews/books/direto-ao-ponto-criando-produtos-de-forma-enxuta.md index f1457bd..2be7c4e 100644 --- a/content/reviews/books/direto-ao-ponto-criando-produtos-de-forma-enxuta.md +++ b/content/reviews/books/direto-ao-ponto-criando-produtos-de-forma-enxuta.md @@ -2,17 +2,47 @@ title = "Direto ao Ponto - criando produtos de forma enxuta - Paulo Caroli" date = 2016-03-26 -category = "review" - [taxonomies] -tags = ["books", "en-au", "paulo caroli"] +tags = ["books", "pt-br", "paulo caroli", "ágil", "reviews"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/23834245-direto-ao-ponto---criando-produtos-de-forma-enxuta): +Um projeto ágil é conduzido através de entregas rápidas e frequentes. Um +projeto bem executado coloca ênfase em entregas de valor de acordo com +objetivos de negócios e os usuários de destaque. Projetos ágeis promovem a +liberação incremental de software: o MVP, o produto viável mínimo, em Inglês +Minimum Viable Product (MVP), a versão mais simples de um produto que pode ser +disponibilizada para o negócio. Mas como realizar o entendimento do MVP e a +iniciação do projeto ágil o mais rápido possível? Como garantir que o time +comece o projeto com entendimento compartilhado, direção, prioridade e um +plano bem definido? + + + {{ stars(stars=3) }} -Quando comecei a ler o livro, me lembrei imediatamente de um vídeo do _Robert C. Martin_ explicando regras de progressão de código conforme os testes unitários avançam: antes de explicar as regras, ele passa por todo o processo de "escrever os testes antes do código", mostrando a evolução do código e nesse ponto TDD faz o maior sentido do mundo. Mas quando ele chega nas regras, você fica pensando se a regra *realmente* faz sentido. +Quando comecei a ler o livro, me lembrei imediatamente de um vídeo do _Robert +C. Martin_ explicando regras de progressão de código conforme os testes +unitários avançam: antes de explicar as regras, ele passa por todo o processo +de "escrever os testes antes do código", mostrando a evolução do código e +nesse ponto TDD faz o maior sentido do mundo. Mas quando ele chega nas regras, +você fica pensando se a regra *realmente* faz sentido. -A mesma coisa aconteceu com o livro: Paulo Caroli começa explicando os vários conceitos e método das metologias enxutas e tudo faz sentido e parece ser a melhor coisa do mundo. Mas depois começa a se aprofundar na inception e você começa a pensar que talvez não faça sentido coletar todas as features e definições e examinar tudo com os stakeholders se métodos ágeis funcionam justamente sabendo que as coisas vão mudar no futuro. Do que adianta planejar, discutir, desenhar e tudo mais quando se sabe que, no produto final, nem todas as features desejadas inicialmente serão usadas ou se durante o desenvolvimento não será detectada a mudança no curso e o resultado final será completamente diferente do planejado inicialmente. +A mesma coisa aconteceu com o livro: Paulo Caroli começa explicando os vários +conceitos e método das metologias enxutas e tudo faz sentido e parece ser a +melhor coisa do mundo. Mas depois começa a se aprofundar na inception e você +começa a pensar que talvez não faça sentido coletar todas as features e +definições e examinar tudo com os stakeholders se métodos ágeis funcionam +justamente sabendo que as coisas vão mudar no futuro. Do que adianta planejar, +discutir, desenhar e tudo mais quando se sabe que, no produto final, nem todas +as features desejadas inicialmente serão usadas ou se durante o +desenvolvimento não será detectada a mudança no curso e o resultado final será +completamente diferente do planejado inicialmente. -E esse ponto em específico nunca é discutido; você fica com um "waterfall" nas mãos sabendo que nem tudo vai ser usado no final -- afinal de contas, essa é a idéia dos métodos ágeis. +E esse ponto em específico nunca é discutido; você fica com um "waterfall" nas +mãos sabendo que nem tudo vai ser usado no final -- afinal de contas, essa é a +idéia dos métodos ágeis. -Então embora o livro descreva como fazer uma inception completa, com o maior número de acertos possíveis, o fato que uma inception não parece se encaixar na metodologia ágil nunca é discutido. \ No newline at end of file +Então embora o livro descreva como fazer uma inception completa, com o maior +número de acertos possíveis, o fato que uma inception não parece se encaixar +na metodologia ágil nunca é discutido. diff --git a/content/reviews/books/django-design-patterns-and-best-practices.md b/content/reviews/books/django-design-patterns-and-best-practices.md index ed5c22d..80bfc43 100644 --- a/content/reviews/books/django-design-patterns-and-best-practices.md +++ b/content/reviews/books/django-design-patterns-and-best-practices.md @@ -2,17 +2,34 @@ title = "Django Design Patterns and Best Practices - Arun Ravindran" date = 2016-07-07 -category = "review" - [taxonomies] -tags = ["books", "en-au", "arun ravindran"] +tags = ["books", "arun ravindran", "python", "django", "web development", "reviews", "design patterns", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/25567728-django-design-patterns-and-best-practices): +Learning how to write better Django code to build more maintainable websites +either takes a lot of experience or familiarity with various design patterns. +Filled with several idiomatic Django patterns, Django Design Patterns and +Best Practices accelerates your journey into the world of web development. + + + {{ stars(stars=3) }} -Although I'm not a fan of design patterns (you know, the GoF one) because people tend replace it to proper thinking. But I do like design patterns for languages and frameworks, because you can use something for a very long time and still not doing it in the right way. +Although I'm not a fan of design patterns (you know, the GoF one) because +people tend replace it to proper thinking. But I do like design patterns for +languages and frameworks, because you can use something for a very long time +and still not doing it in the right way. -The book has an interesting premise: Explain a bit something, point a problem, a solution, expand the problem and expand the solution. The problem is that some problems seem really shoe horned to certain solutions. Also, some common problems are not talked at all, like using CSRF with Ajax -- something the author mentions people shouldn't do (disable CSRF) on Ajax requests. +The book has an interesting premise: Explain a bit something, point a problem, +a solution, expand the problem and expand the solution. The problem is that +some problems seem really shoe horned to certain solutions. Also, some common +problems are not talked at all, like using CSRF with Ajax -- something the +author mentions people shouldn't do (disable CSRF) on Ajax requests. -On the other hand, the book focus on the the most recent versions (well, almost). Instead of going in the safe road of Python 2, the book focus on Python 3 -- and, to be honest, there isn't much difference between Django with Python 3 and Django with Python 2. +On the other hand, the book focus on the the most recent versions (well, +almost). Instead of going in the safe road of Python 2, the book focus on +Python 3 -- and, to be honest, there isn't much difference between Django with +Python 3 and Django with Python 2. -Is not a bad book, but the really interesting things seem to be left out. \ No newline at end of file +Is not a bad book, but the really interesting things seem to be left out. diff --git a/content/reviews/books/dogfight-how-apple-and-google-went-to-war-and-started-a-revolution.md b/content/reviews/books/dogfight-how-apple-and-google-went-to-war-and-started-a-revolution.md index 288a294..1a5c9f2 100644 --- a/content/reviews/books/dogfight-how-apple-and-google-went-to-war-and-started-a-revolution.md +++ b/content/reviews/books/dogfight-how-apple-and-google-went-to-war-and-started-a-revolution.md @@ -2,17 +2,40 @@ title = "Dogfight: How Apple and Google Went to War and Started a Revolution - Fred Vogelstein" date = 2014-03-07 -category = "review" - [taxonomies] -tags = ["books", "en-au", "fred vogelstein"] +tags = ["books", "fred vogelstein", "reviews", "it", "apple", "google"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/17332226-dogfight): +The rise of smartphones and tablets has altered the business of making +computers. At the center of this change are Apple and Google, two companies +whose philosophies, leaders, and commercial acumen have steamrolled the +competition. In the age of the Android and the iPad, these corporations are +locked in a feud that will play out not just in the marketplace but in the +courts and on screens around the world. + + + {{ stars(stars=2) }} -It starts as a very interesting story, telling the behind the scenes stories about the first iPhone and the creation of Android. Then it derails and do two stupid things: starts brown nosing one side and focus on a single region. +It starts as a very interesting story, telling the behind the scenes stories +about the first iPhone and the creation of Android. Then it derails and do two +stupid things: starts brown nosing one side and focus on a single region. -Mid book you'll see how Jobs was aggressive, how Apple was nasty and how Page, Brin and Schmidt were open and Google was an innovative company. The author doesn't deny the effect of iPhones and iPads, but focus solely on what others were doing instead of giving at least some acknowledgement too the company that created such devices. And yes, I know I sound like a fanboy, but when the author talks about Android it is never about its effects, only how cool and innovative and customisable it is. This very much makes the whole book look one sided, in a non funny way. +Mid book you'll see how Jobs was aggressive, how Apple was nasty and how Page, +Brin and Schmidt were open and Google was an innovative company. The author +doesn't deny the effect of iPhones and iPads, but focus solely on what others +were doing instead of giving at least some acknowledgement too the company +that created such devices. And yes, I know I sound like a fanboy, but when the +author talks about Android it is never about its effects, only how cool and +innovative and customisable it is. This very much makes the whole book look +one sided, in a non funny way. -The other point is the effects of mobile ecosystem. Everything focus solely in the USA. It's really weird for someone read about Google Music and its dent on Apple music stronghold when your country have no access to Google Music since its inception 3 or so years ago. +The other point is the effects of mobile ecosystem. Everything focus solely in +the USA. It's really weird for someone read about Google Music and its dent on +Apple music stronghold when your country have no access to Google Music since +its inception 3 or so years ago. -If the whole book focused on the behind the scenes stories and how they intertwine, it would be a really interesting book. But a narrowed vision and the author personal opinion leaking through the story really ruins everything. \ No newline at end of file +If the whole book focused on the behind the scenes stories and how they +intertwine, it would be a really interesting book. But a narrowed vision and +the author personal opinion leaking through the story really ruins everything. diff --git a/content/reviews/books/dossie-jung.md b/content/reviews/books/dossie-jung.md index 9738977..63f8e11 100644 --- a/content/reviews/books/dossie-jung.md +++ b/content/reviews/books/dossie-jung.md @@ -2,17 +2,38 @@ title = "Dossiê Jung - Elizabeth Mednicoff" date = 2017-03-21 -category = "review" - [taxonomies] -tags = ["books", "en-au", "elizabeth mednicoff"] +tags = ["books", "pt-br", "elizabeth mednicoff", "reviews", "psicologia", "carl jung"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/23356314-dossi-jung): +Nesta obra, a autora descreve fatos valiosos a respeito do criador da +Psicologia Analítica, resultando em um livro rico não apenas como fonte de +informação, mas também como objeto de reflexão a respeito do ser humano e de +como ele lida com seus problemas e se relaciona com o mundo. Da infância e +juventude à idade adulta e seus últimos dias, o leitor conhecerá a trajetória +de vida do psiquiatra suíço que desde jovem se interessou por filosofia, +literatura e foi amigo de Freud. Além disso, são relatados pontos importantes +sobre a escola analítica da Psicologia fundada por Jung, incluindo os +conceitos do Inconsciente Individual e Coletivo, os Arquétipos, Anima e +Animus, o Self, a Teoria dos Tipos Psicológicos, a Dinâmica da Personalidade e +como se dá a sua formação. + + + {{ stars(stars=1) }} Vários problemas com a estrutura do livro. -Primeiro, não é um "Dossiê Jung". A parte sobre Jung, a pessoa, termina logo nos primeiro quinto do livro. A vida do médico/psicólogo nunca mais é revista. +Primeiro, não é um "Dossiê Jung". A parte sobre Jung, a pessoa, termina logo +nos primeiro quinto do livro. A vida do médico/psicólogo nunca mais é revista. -Depois disso, começa uma explicação da psicologia analítica, criada por Jung, com todos os seus conceitos... E nenhum exemplo claro. Por exemplo, na parte de símbolos, é comentado que existem símbolos fixos, mas quais são esses símbolos (pelo menos, os primordias, como a casa e a mandala) não são citados. Então fica tudo em conceitos e nada palpável. +Depois disso, começa uma explicação da psicologia analítica, criada por Jung, +com todos os seus conceitos... E nenhum exemplo claro. Por exemplo, na parte +de símbolos, é comentado que existem símbolos fixos, mas quais são esses +símbolos (pelo menos, os primordias, como a casa e a mandala) não são citados. +Então fica tudo em conceitos e nada palpável. -E ainda, existe muito mais opinião ("creio" em alguns pontos) e falta de conteúdo direto (como indicar ao leitor para "procurar na web") que realmente tiram a ideia de que é um trabalho completo. \ No newline at end of file +E ainda, existe muito mais opinião ("creio" em alguns pontos) e falta de +conteúdo direto (como indicar ao leitor para "procurar na web") que realmente +tiram a ideia de que é um trabalho completo. diff --git a/content/reviews/books/dragons-winter.md b/content/reviews/books/dragons-winter.md index a1ff99f..4170cf1 100644 --- a/content/reviews/books/dragons-winter.md +++ b/content/reviews/books/dragons-winter.md @@ -3,7 +3,7 @@ title = "Dragon's Winter - Elizabeth A. Lynn" date = 2019-08-14 [taxonomies] -tags = ["en-au", "books", "reviews", "fantasy", "elizabeth a lynn"] +tags = ["books", "reviews", "fantasy", "elizabeth a lynn"] +++ [Goodreads Summary](https://www.goodreads.com/book/show/22746453-dragon-s-winter): diff --git a/content/reviews/books/elon-musk-como-o-ceo-bilionario-da-spacex-e-da-tesla-esta-moldando-o-nosso-futuro.md b/content/reviews/books/elon-musk-como-o-ceo-bilionario-da-spacex-e-da-tesla-esta-moldando-o-nosso-futuro.md index 2b5a05c..61ae250 100644 --- a/content/reviews/books/elon-musk-como-o-ceo-bilionario-da-spacex-e-da-tesla-esta-moldando-o-nosso-futuro.md +++ b/content/reviews/books/elon-musk-como-o-ceo-bilionario-da-spacex-e-da-tesla-esta-moldando-o-nosso-futuro.md @@ -2,17 +2,41 @@ title = "Elon Musk: Como o CEO bilionário da SpaceX e da Tesla está moldando o nosso futuro - Ashlee Vance" date = 2016-02-17 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ashlee vance"] +tags = ["books", "pt-br", "ashlee vance", "reviews", "elon musk", "biografia"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/26866506-elon-musk): +Elon Musk é o empreendedor mais ousado de nosso tempo. Uma mistura de Thomas +Edison, Henry Ford, Howard Hughes e Steve Jobs, ele é o homem por trás dos +cobiçados esportivos elétricos da Tesla Motors, dos painéis e baterias de +energia solar popularizados pela SolarCity e dos foguetes espaciais da SpaceX, +construídos do zero com recursos privados e muito mais baratos que qualquer +versão já lançada pelas agências governamentais. Entre as próximas metas de +Musk está a colonização de Marte. + + + {{ stars(stars=4) }} -Elon é uma figura que eu respeito pela decisão, a muito tempo, de, inicialmente, fazer um carro elétrico num mundo que já sofre demais com a queima de combustíveis fósseis e, depois, por abrir as patentes das baterias que alimentam esses carros. +Elon é uma figura que eu respeito pela decisão, a muito tempo, de, +inicialmente, fazer um carro elétrico num mundo que já sofre demais com a +queima de combustíveis fósseis e, depois, por abrir as patentes das baterias +que alimentam esses carros. -Entretanto, o livro não fala realmente de Elon Musk. Essa "biografia" aborda muito mais as empresas de Musk (o que o autor chama, mais tarde, de "Musk Co") do que a pessoa Elon Musk. Detalhes sobre a vida, como pensa e tudo mais ficam relegados a segundo plano enquanto que a história da SpaceX e da Tesla tomam a frente. Sim, é uma forma de entender a pessoa vendo as decisões dela sobre produtos importante, mas pouco se fala das decisões que Musk tomou sobre as empresas e sim as decisões de outras pessoas sobre as empresas que ele comanda. No fim, sobra muito da empresa e pouco da pessoa. +Entretanto, o livro não fala realmente de Elon Musk. Essa "biografia" aborda +muito mais as empresas de Musk (o que o autor chama, mais tarde, de "Musk Co") +do que a pessoa Elon Musk. Detalhes sobre a vida, como pensa e tudo mais ficam +relegados a segundo plano enquanto que a história da SpaceX e da Tesla tomam a +frente. Sim, é uma forma de entender a pessoa vendo as decisões dela sobre +produtos importante, mas pouco se fala das decisões que Musk tomou sobre as +empresas e sim as decisões de outras pessoas sobre as empresas que ele +comanda. No fim, sobra muito da empresa e pouco da pessoa. -Detalhes da pessoa são somente abertos nos apêndices, onde o autor coloca descrições completas das conversas com Elon e finalmente se tem uma idéia de como ele pensa, mesmo que superficialmente por se tratar de pontos específicos de discussão. +Detalhes da pessoa são somente abertos nos apêndices, onde o autor coloca +descrições completas das conversas com Elon e finalmente se tem uma idéia de +como ele pensa, mesmo que superficialmente por se tratar de pontos específicos +de discussão. -É um livro interessante para entender a SpaceX e a Tesla, mas pouco para se entender Elon Musk. \ No newline at end of file +É um livro interessante para entender a SpaceX e a Tesla, mas pouco para se +entender Elon Musk. diff --git a/content/reviews/books/emotions-revealed-understanding-faces-and-feelings.md b/content/reviews/books/emotions-revealed-understanding-faces-and-feelings.md index cc8f7ee..cec8ba2 100644 --- a/content/reviews/books/emotions-revealed-understanding-faces-and-feelings.md +++ b/content/reviews/books/emotions-revealed-understanding-faces-and-feelings.md @@ -2,19 +2,40 @@ title = "Emotions Revealed: Understanding Faces and Feelings - Paul Ekman" date = 2014-12-20 -category = "review" - [taxonomies] -tags = ["books", "en-au", "paul ekman"] +tags = ["books", "paul ekman", "psychology", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/156462.Emotions_Revealed): +A renowned expert in nonverbal communication, Paul Ekman led a revolution in +our scientific understanding of emotions. In Emotions Revealed, he assembles +his research and theories to provide a comprehensive look at the evolutionary +roots of human emotions, including anger, sadness, fear, disgust, and +happiness. + + + {{ stars(stars=3) }} **Emotions: Learning, therapy and socialization** -There is one thing weird about this book: although it explores the expressions on people's faces, going through lenghty explanations about what they mean and which context they may happen, there are also parts explaining why you would feel something like that and how to react when you notice people doing them. It's part explanation about emotions, part teaching you about your own emotions (like in a therapy session) and part how to react when people show them (socialization). In a full package. +There is one thing weird about this book: although it explores the expressions +on people's faces, going through lenghty explanations about what they mean and +which context they may happen, there are also parts explaining why you would +feel something like that and how to react when you notice people doing them. +It's part explanation about emotions, part teaching you about your own +emotions (like in a therapy session) and part how to react when people show +them (socialization). In a full package. -The problem I found is not about the book, but about the Kindle edition: Because we are exploring expressions in people's faces, we need images. But images on Kindle is terrible and in very low quality. It makes kinda hard to see that little muscle that you move only when you're feeling some emotion when the image showing it have almost no details due quality. +The problem I found is not about the book, but about the Kindle edition: +Because we are exploring expressions in people's faces, we need images. But +images on Kindle is terrible and in very low quality. It makes kinda hard to +see that little muscle that you move only when you're feeling some emotion +when the image showing it have almost no details due quality. -There is a test in the end of the book, explaining exactly what you should be looking for. The problem is, again, the photo quality in the book. +There is a test in the end of the book, explaining exactly what you should be +looking for. The problem is, again, the photo quality in the book. -It's an interesting book, specially when it shows that our reactions (face reactions) to some emotions happen in every society, every culture, but hard to follow due those bad images. \ No newline at end of file +It's an interesting book, specially when it shows that our reactions (face +reactions) to some emotions happen in every society, every culture, but hard +to follow due those bad images. diff --git a/content/reviews/books/eon-the-way-1.md b/content/reviews/books/eon-the-way-1.md index 0a0c434..bf0f8b4 100644 --- a/content/reviews/books/eon-the-way-1.md +++ b/content/reviews/books/eon-the-way-1.md @@ -2,15 +2,31 @@ title = "Eon (The Way, #1) - Greg Bear" date = 2018-04-12 -category = "review" - [taxonomies] -tags = ["books", "en-au", "greg bear"] +tags = ["books", "greg bear", "reviews", "the way", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/840278.Eon): +The 21st century was on the brink of nuclear confrontation when the 300 +kilometer-long stone flashed out of nothingness and into Earth's orbit. NASA, +NATO, and the UN sent explorers to the asteroid's surface...and discovered +marvels and mysteries to drive researchers mad. + + + {{ stars(stars=2) }} -_Rendezvous with Rama_. It's all I could think while reading this book. I mean, it's a very large, strange object, which humans from Earth get inside and, while the story progresses, suddenly there are some kind of benevolent aliens, but the real monsters are the humans, in the end. And, as Rendezvous, there is a lot of over-describing stuff that is not actually important for the plot. +_Rendezvous with Rama_. It's all I could think while reading this book. I +mean, it's a very large, strange object, which humans from Earth get inside +and, while the story progresses, suddenly there are some kind of benevolent +aliens, but the real monsters are the humans, in the end. And, as Rendezvous, +there is a lot of over-describing stuff that is not actually important for the +plot. -Sure, there are some twists, like who the aliens really are (while later in the Rama series you get *why* the aliens built the spaceship in the first place) and while the over-descriptions of how the aliens (in this book) look like, even if they are curious, show a lot of creativity from the author, they still are over-descriptions that add absolutely nothing to the plot. +Sure, there are some twists, like who the aliens really are (while later in +the Rama series you get *why* the aliens built the spaceship in the first +place) and while the over-descriptions of how the aliens (in this book) look +like, even if they are curious, show a lot of creativity from the author, they +still are over-descriptions that add absolutely nothing to the plot. -In the end, curious, but boring. \ No newline at end of file +In the end, curious, but boring. diff --git a/content/reviews/books/films-from-the-future.md b/content/reviews/books/films-from-the-future.md index 722b007..92a6804 100644 --- a/content/reviews/books/films-from-the-future.md +++ b/content/reviews/books/films-from-the-future.md @@ -5,7 +5,7 @@ date = 2018-11-29 category = "review" [taxonomies] -tags = ["books", "en-au", "andrew maynard"] +tags = ["books", "andrew maynard"] +++ [GoodReads summary](https://www.goodreads.com/book/show/41045578-films-from-the-future): diff --git a/content/reviews/books/future-shock-future-shock-1.md b/content/reviews/books/future-shock-future-shock-1.md index 998ea26..c293b42 100644 --- a/content/reviews/books/future-shock-future-shock-1.md +++ b/content/reviews/books/future-shock-future-shock-1.md @@ -2,15 +2,33 @@ title = "Future Shock (Future Shock, #1) - Elizabeth Briggs" date = 2018-06-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "elizabeth briggs"] +tags = ["books", "elizabeth briggs", "reviews", "future shock", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/26722944-future-shock): +Elena Martinez has street smarts, the ability for perfect recall, and a +deadline: if she doesn’t find a job before she turns eighteen, she’ll be +homeless. But then she gets an unexpected offer from Aether Corporation, the +powerful Los Angeles tech giant. Along with four other recruits—Adam, Chris, +Trent, and Zoe—Elena is being sent on a secret mission to bring back data from +the future. All they have to do is get Aether the information they need, and +the five of them will be set for life. It’s an offer Elena can’t refuse. + + + {{ stars(stars=3) }} -The basic plot is: A group of teens with special talents is chosen to go to the future but something something and then they are happily ever after. +The basic plot is: A group of teens with special talents is chosen to go to +the future but something something and then they are happily ever after. -So... Yes, it's a time travel story, but it goes to the future instead of the past, which is something new for me. And there is a plot twist in the end, but it's not big. And the protagonists are teens and, even if it's explained why (with a bunch of technobabble, that is)... meh. And their "talents" are not that so important to the plot -- if they were some very clever adults, the plot would still work the same. +So... Yes, it's a time travel story, but it goes to the future instead of the +past, which is something new for me. And there is a plot twist in the end, but +it's not big. And the protagonists are teens and, even if it's explained why +(with a bunch of technobabble, that is)... meh. And their "talents" are not +that so important to the plot -- if they were some very clever adults, the +plot would still work the same. -But the writing is pretty damn good, even when it lags in the end and you feel you can jump whole paragraphs without missing the story. But it's not crumpled, and it's not full of useless descriptions. \ No newline at end of file +But the writing is pretty damn good, even when it lags in the end and you feel +you can jump whole paragraphs without missing the story. But it's not +crumpled, and it's not full of useless descriptions. diff --git a/content/reviews/books/galaxy-in-flames.md b/content/reviews/books/galaxy-in-flames.md index ef85565..72a4416 100644 --- a/content/reviews/books/galaxy-in-flames.md +++ b/content/reviews/books/galaxy-in-flames.md @@ -3,7 +3,7 @@ title = "Galaxy in Flames, Ben Counter" date = 2019-11-20 [taxonomies] -tags = ["en-au", "books", "reviews", "horus heresy", "ben counter"] +tags = ["books", "reviews", "horus heresy", "ben counter", "scifi", "warhammer 40000"] +++ [GoodReads Summary](https://www.goodreads.com/book/show/815091.Galaxy_in_Flames): diff --git a/content/reviews/books/genius-the-life-and-science-of-richard-feynman.md b/content/reviews/books/genius-the-life-and-science-of-richard-feynman.md index e105a1a..dfa8350 100644 --- a/content/reviews/books/genius-the-life-and-science-of-richard-feynman.md +++ b/content/reviews/books/genius-the-life-and-science-of-richard-feynman.md @@ -2,21 +2,43 @@ title = "Genius: The Life and Science of Richard Feynman - James Gleick" date = 2018-10-28 -category = "review" - [taxonomies] -tags = ["books", "en-au", "james gleick"] +tags = ["books", "james gleick", "richard feynman", "reviews", "biography", "history"] +++ -{{ stars(stars=2) }} -Biographies (even auto-biographies) are not without problems. But it takes a lot of effort to lose the mark. +[GoodReads Summary](https://www.goodreads.com/book/show/98685.Genius): +An illuminating portrayal of Richard Feynman—a giant of twentieth century +physics—from his childhood tinkering with radios, to his vital work on the +Manhattan Project and beyond. -Imagine that you're drawing the life time of someone; you can't use a pen with a thin point, otherwise you'll end up with simple "they did this, they did that" with dates, which doesn't give the proper understanding and context of why the subject did this and that. In the same vein, you can't use a pen larger than a marker, otherwise you'll spend too much time on things that are not related to the subject. + -And this book draw the life of Feynman with a brush. +{{ stars(stars=2) }} + +Biographies (even auto-biographies) are not without problems. But it takes a +lot of effort to lose the mark. -There is a whole chapter about absolutely nothing but a discussion about what "genius" mean, which seems more targeted to explain the book title than what happened to Feynman -- or even if his colleagues and family though he was a genius, for whatever meaning of the word. +Imagine that you're drawing the life time of someone; you can't use a pen with +a thin point, otherwise you'll end up with simple "they did this, they did +that" with dates, which doesn't give the proper understanding and context of +why the subject did this and that. In the same vein, you can't use a pen +larger than a marker, otherwise you'll spend too much time on things that are +not related to the subject. -There are other chapters than, instead of focusing of Feynman, focus on other subjects, in points that do not related to Feynman directly. The last chapter, focused on the Challenger explosion, in which Feynman was part of the commission to explain the explosion, talks a lot more about NASA politics than Feynman. +And this book draw the life of Feynman with a brush. -And, on top of that, the author is very lose with poetic prose instead of being direct to the point. Also, the lack of a continuous timeline, with the points moving back and forth through time, makes it hard to understand when things happen. \ No newline at end of file +There is a whole chapter about absolutely nothing but a discussion about what +"genius" mean, which seems more targeted to explain the book title than what +happened to Feynman -- or even if his colleagues and family though he was a +genius, for whatever meaning of the word. + +There are other chapters than, instead of focusing of Feynman, focus on other +subjects, in points that do not related to Feynman directly. The last chapter, +focused on the Challenger explosion, in which Feynman was part of the +commission to explain the explosion, talks a lot more about NASA politics than +Feynman. + +And, on top of that, the author is very lose with poetic prose instead of +being direct to the point. Also, the lack of a continuous timeline, with the +points moving back and forth through time, makes it hard to understand when +things happen. diff --git a/content/reviews/books/getting-started-with-meteorjs-javascript-framework-second-edition.md b/content/reviews/books/getting-started-with-meteorjs-javascript-framework-second-edition.md index b20e7d6..32d22f0 100644 --- a/content/reviews/books/getting-started-with-meteorjs-javascript-framework-second-edition.md +++ b/content/reviews/books/getting-started-with-meteorjs-javascript-framework-second-edition.md @@ -2,13 +2,26 @@ title = "Getting Started with Meteor.js JavaScript Framework - Second Edition - Isaac Strack" date = 2016-03-25 -category = "review" - [taxonomies] -tags = ["books", "en-au", "isaac strack"] +tags = ["books", "isaac strack", "meter.js", "javascript", "reviews", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/25903452-getting-started-with-meteor-js-javascript-framework---second-edition): +Learn one of the most up-to-date JavaScript platforms, with easy to follow, +step-by-step instructions Familiarize yourself with Meteor’s new and improved +features Create dynamic, multi-user applications in JavaScript. + + + {{ stars(stars=4) }} -I must say, I'm confused about something: Either the book is really shallow or there are no "gotchas" with Meteor. 'Cause the book goes all the way from creating a single application from start to end, keep it straight, doesn't add any bullshit, add external dependencies, packages it and then deploys either on the meteor structure or in custom server. +I must say, I'm confused about something: Either the book is really shallow or +there are no "gotchas" with Meteor. 'Cause the book goes all the way from +creating a single application from start to end, keep it straight, doesn't add +any bullshit, add external dependencies, packages it and then deploys either +on the meteor structure or in custom server. -So, again, either Meteor is so simple that everything is already packaged or the book is shallow and doesn't go deep into problems you may find. I can't really know, after reading it, which one (although I'd bet my money on the first). \ No newline at end of file +So, again, either Meteor is so simple that everything is already packaged or +the book is shallow and doesn't go deep into problems you may find. I can't +really know, after reading it, which one (although I'd bet my money on the +first). diff --git a/content/reviews/books/getting-things-done-the-art-of-stress-free-productivity.md b/content/reviews/books/getting-things-done-the-art-of-stress-free-productivity.md index 84d0cdf..9ea229b 100644 --- a/content/reviews/books/getting-things-done-the-art-of-stress-free-productivity.md +++ b/content/reviews/books/getting-things-done-the-art-of-stress-free-productivity.md @@ -2,25 +2,51 @@ title = "Getting Things Done: The Art of Stress-Free Productivity - David Allen" date = 2015-03-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "david allen"] +tags = ["books", "david allen", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/1633.Getting_Things_Done): +In today's world, yesterday's methods just don't work. In Getting Things Done, +veteran coach and management consultant David Allen shares the breakthrough +methods for stress-free performance that he has introduced to tens of +thousands of people across the country. Allen's premise is simple: our +productivity is directly proportional to our ability to relax. Only when our +minds are clear and our thoughts are organized can we achieve effective +productivity and unleash our creative potential. + + + {{ stars(stars=3) }} -As a method, GTD is damn obvious to follow: Write things down so you don't need to keep thinking that you need to remember something, which would just lead into a constant need of keeping parts of your brain working on remembering instead of producing stuff; focus on what you should do next to complete said things you wrote down; and so on. +As a method, GTD is damn obvious to follow: Write things down so you don't +need to keep thinking that you need to remember something, which would just +lead into a constant need of keeping parts of your brain working on +remembering instead of producing stuff; focus on what you should do next to +complete said things you wrote down; and so on. -Part of the whole I was already following, so learning a few more tricks was really welcomed. +Part of the whole I was already following, so learning a few more tricks was +really welcomed. The problem here is the telling itself. -There are references to PDAs, like it was something not so common. Right now, almost everyone has a PDA in their pocket, although we call them "smartphones" instead of PDAs; there are references to "common" binders and rolodexes and that kind of furniture that, in today's world, is a pretty rare thing and most of the stuff we deal each day is digital. +There are references to PDAs, like it was something not so common. Right now, +almost everyone has a PDA in their pocket, although we call them "smartphones" +instead of PDAs; there are references to "common" binders and rolodexes and +that kind of furniture that, in today's world, is a pretty rare thing and most +of the stuff we deal each day is digital. -There are some topics which are largely just propaganda for the method itself instead of going straight into it to give people an general idea of how things work and then going deeper (he does it later, but the very start is boring as hell). +There are some topics which are largely just propaganda for the method itself +instead of going straight into it to give people an general idea of how things +work and then going deeper (he does it later, but the very start is boring as +hell). -Also, some final topics are mostly "One of my clients said she couldn't understand how she lived till this day doing things not GTD" or "I do this 'cause I like it", which although good to know, it's not representative of the method itself. +Also, some final topics are mostly "One of my clients said she couldn't +understand how she lived till this day doing things not GTD" or "I do this +'cause I like it", which although good to know, it's not representative of the +method itself. -So while GTD is a pretty damn good method to keep things organized, the book that describes this is not well written, IMHO. +So while GTD is a pretty damn good method to keep things organized, the book +that describes this is not well written, IMHO. -Get it for the methodology, and be ready to skip a lot of useless stuff. \ No newline at end of file +Get it for the methodology, and be ready to skip a lot of useless stuff. diff --git a/content/reviews/books/greek-mythology-explained.md b/content/reviews/books/greek-mythology-explained.md index ebb0596..6e57662 100644 --- a/content/reviews/books/greek-mythology-explained.md +++ b/content/reviews/books/greek-mythology-explained.md @@ -3,7 +3,7 @@ title = "Greek Mythology Explained: A Deeper Look at Classical Greek Lore and My date = 2019-01-05 [taxonomies] -tags = ["en-au", "book", "reviews", "greek mythology", "marios christou", "david ramenah"] +tags = ["book", "reviews", "greek mythology", "marios christou", "david ramenah"] +++ [GoodReads Summary](https://www.goodreads.com/book/show/41822694-greek-mythology-explained): diff --git a/content/reviews/books/guia-politicamente-incorreto-da-historia-do-mundo.md b/content/reviews/books/guia-politicamente-incorreto-da-historia-do-mundo.md index 1fff04a..91a773a 100644 --- a/content/reviews/books/guia-politicamente-incorreto-da-historia-do-mundo.md +++ b/content/reviews/books/guia-politicamente-incorreto-da-historia-do-mundo.md @@ -5,22 +5,61 @@ date = 2016-04-29 category = "review" [taxonomies] -tags = ["books", "en-au", "leandro narloch"] +tags = ["books", "pt-br", "leandro narloch", "reviews", "história", "history"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18172387-guia-politicamente-incorreto-da-hist-ria-do-mundo): +Este livro é um guia contra a doutrinação que muitos brasileiros sofreram na +escola. Não tem a pretensão de contar a história do mundo: seu alvo são os +principais mitos sobre os últimos 2 mil anos que, apesar de terem sido +derrubados há muito tempo por historiadores, prevalecem nos livros didáticos, +nas provas do Enem, nas conversas de bar. + + + {{ stars(stars=1) }} -O título mais correto para este livro seria: "Narloch e as Fantásticas Falácias para Provar Pontos". +O título mais correto para este livro seria: "Narloch e as Fantásticas +Falácias para Provar Pontos". -O livro até começa bem, falando historicamente de Nero e da famigerada queima de Roma. +O livro até começa bem, falando historicamente de Nero e da famigerada queima +de Roma. -A partir desse ponto, no entanto, a coisa desanda para um nível de falácias que, se fossem analisadas, poderiam gerar um livro com o dobro do tamanho deste. +A partir desse ponto, no entanto, a coisa desanda para um nível de falácias +que, se fossem analisadas, poderiam gerar um livro com o dobro do tamanho +deste. -Falando em Galileu, o autor debocha do fato dele (Galileu) ganhar a vida escrevendo horóscopos. Mais tarde, insinua a homossexualidade de Ghandi, e afirma "apesar disso, não podemos criticar Ghandi por suas escolhas sexuais" (ou algo desse tipo). Sim, não é possível, porque isso é chamado *ad hominem* -- que, estranhamente, é o mesmo que o autor fez com Galileu! Vale pra um, não vale pro outro. +Falando em Galileu, o autor debocha do fato dele (Galileu) ganhar a vida +escrevendo horóscopos. Mais tarde, insinua a homossexualidade de Ghandi, e +afirma "apesar disso, não podemos criticar Ghandi por suas escolhas sexuais" +(ou algo desse tipo). Sim, não é possível, porque isso é chamado *ad hominem* +-- que, estranhamente, é o mesmo que o autor fez com Galileu! Vale pra um, não +vale pro outro. -Outro caso: Afirmar que a revolução industrial ajudou os pobres da Inglaterra, e logo depois afirma que a grande maioria que saiu do campo e foi procurar vida melhor na cidade, morreu. De forma alguma estou criticando a revolução industrial, mas quando "a grande maioria" morre por algo, como é que ela pode "ter feito bem"? +Outro caso: Afirmar que a revolução industrial ajudou os pobres da Inglaterra, +e logo depois afirma que a grande maioria que saiu do campo e foi procurar +vida melhor na cidade, morreu. De forma alguma estou criticando a revolução +industrial, mas quando "a grande maioria" morre por algo, como é que ela pode +"ter feito bem"? -Essas imbecilidades que beiram a infantilidade nesses 4 primeiros capítulos fazem com que o resto do livro fique com uma sensação ruim ao ler. Não só falácias e erros crasos de lógica percorrem o livro inteiro, a postura política do autor também fica extremamente clara. Se houvesse, logo de cara, um aviso sobre isso, não seria grande problema; o problema ocorre que o livro aparentemente escolheu fatos justamente para justificar a postura política ao invés de, obviamente, focar na *história do mundo* (que está ali no título). +Essas imbecilidades que beiram a infantilidade nesses 4 primeiros capítulos +fazem com que o resto do livro fique com uma sensação ruim ao ler. Não só +falácias e erros crasos de lógica percorrem o livro inteiro, a postura +política do autor também fica extremamente clara. Se houvesse, logo de cara, +um aviso sobre isso, não seria grande problema; o problema ocorre que o livro +aparentemente escolheu fatos justamente para justificar a postura política ao +invés de, obviamente, focar na *história do mundo* (que está ali no título). -Não só a qualidade lógica do conteúdo tem que ser constantemente questionada, mas a versão do Kindle deixa muito a desejar. Além de hifenizar palavras em lugares errados ("escol-ha", por exemplo), o autor decidiu colocar parágrafos com bordas mais largas de forma alternativa (algumas vezes, o texto fica todo à esquerda, outras todo a direita), usa 4 tamanhos diferentes de fontes e, randomicamente, deixa uma palavra em negrito. Só faltou o texto inteiro estar em comic sans. +Não só a qualidade lógica do conteúdo tem que ser constantemente questionada, +mas a versão do Kindle deixa muito a desejar. Além de hifenizar palavras em +lugares errados ("escol-ha", por exemplo), o autor decidiu colocar parágrafos +com bordas mais largas de forma alternativa (algumas vezes, o texto fica todo +à esquerda, outras todo a direita), usa 4 tamanhos diferentes de fontes e, +randomicamente, deixa uma palavra em negrito. Só faltou o texto inteiro estar +em comic sans. -Não que o livro não tenha seu conjunto de informações, mas o fato de ser, especificamente, um amontoado de situações da história usados simplesmente para provar (com erros de lógica que fariam os pensadores gregos rirem até a morrerem) a posição do política do autor realmente destroem qualquer consideração que deveria ser feita ao conteúdo real. \ No newline at end of file +Não que o livro não tenha seu conjunto de informações, mas o fato de ser, +especificamente, um amontoado de situações da história usados simplesmente +para provar (com erros de lógica que fariam os pensadores gregos rirem até a +morrerem) a posição do política do autor realmente destroem qualquer +consideração que deveria ser feita ao conteúdo real. diff --git a/content/reviews/books/hadoop-in-practice-manning.md b/content/reviews/books/hadoop-in-practice-manning.md index 9f131b2..8108430 100644 --- a/content/reviews/books/hadoop-in-practice-manning.md +++ b/content/reviews/books/hadoop-in-practice-manning.md @@ -1,18 +1,46 @@ +++ -title = "Hadoop in Practice (Manning) - Alex Holmes" +title = "Hadoop in Practice - Alex Holmes" date = 2018-02-16 -category = "review" - [taxonomies] -tags = ["books", "en-au", "alex holmes"] +tags = ["books", "alex holmes", "reviews", "ti", "hadoop", "big data"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/13496907-hadoop-in-practice): +Hadoop in Practice collects nearly 100 Hadoop examples and presents them in a +problem/solution format. Each technique addresses a specific task you'll face, +like querying big data using Pig or writing a log file loader. You'll explore +each problem step by step, learning both how to build and deploy that specific +solution along with the thinking that went into its design. As you work +through the tasks, you'll find yourself growing more comfortable with Hadoop +and at home in the world of big data. + + + {{ stars(stars=1) }} -First thing: This is not about how to deal with Hadoop in a real environment; this a cookbook of recipes for working with Hadoop, some of them that you won't ever use. +First thing: This is not about how to deal with Hadoop in a real environment; +this a cookbook of recipes for working with Hadoop, some of them that you +won't ever use. -Second: The book uses a structure of "Explanation/Problem/Solution/Discussion". While the formula usually works, here is simply to add more words, because "Problem" is tailored exclusively to pair with the "Explanation". Not only that but "Solution" is basically a rehearsal of the "Explanation". Something like "Hadoop comes with it's own class for dealing with X file format; Problem: You have files in the X format and want to process them in Hadoop; Solution: Use the classes in Hadoop". This basically throw the whole structure under a bus. +Second: The book uses a structure of +"Explanation/Problem/Solution/Discussion". While the formula usually works, +here is simply to add more words, because "Problem" is tailored exclusively to +pair with the "Explanation". Not only that but "Solution" is basically a +rehearsal of the "Explanation". Something like "Hadoop comes with it's own +class for dealing with X file format; Problem: You have files in the X format +and want to process them in Hadoop; Solution: Use the classes in Hadoop". This +basically throw the whole structure under a bus. -Third: There is plenty of code examples, and most are terrible. I don't mean "The code doesn't compile" or "It doesn't follow any good practices". I mean it uses some cutesy arrows to point to some pieces of code, which means it's an image instead of a real code, which means you can't copy'n'paste if needed. Also, those arrows could be easily be converted to comments, except most comments would fall into the "i = i + 1; // increments i" category -- useless comments pointing to obvious things. If it would tell you *why* you're incrementing "i" instead of what it's doing, it would at least be interesting. +Third: There is plenty of code examples, and most are terrible. I don't mean +"The code doesn't compile" or "It doesn't follow any good practices". I mean +it uses some cutesy arrows to point to some pieces of code, which means it's +an image instead of a real code, which means you can't copy'n'paste if needed. +Also, those arrows could be easily be converted to comments, except most +comments would fall into the "i = i + 1; // increments i" category -- useless +comments pointing to obvious things. If it would tell you *why* you're +incrementing "i" instead of what it's doing, it would at least be interesting. -There may be something useful there if you have a specific problem with Hadoop. But if you have a single, specific problem, you'd Google it instead of buying a book with a bunch of other solutions that doesn't affect you. \ No newline at end of file +There may be something useful there if you have a specific problem with +Hadoop. But if you have a single, specific problem, you'd Google it instead of +buying a book with a bunch of other solutions that doesn't affect you. diff --git a/content/reviews/books/handson-microservices-with-rust.md b/content/reviews/books/handson-microservices-with-rust.md index b225417..7fc143f 100644 --- a/content/reviews/books/handson-microservices-with-rust.md +++ b/content/reviews/books/handson-microservices-with-rust.md @@ -3,9 +3,13 @@ title = "Hands-On Microservices with Rust - Denis Kolodin" date = 2019-03-03 [taxonomies] -tags = ["reviews", "books", "en-au", "rust", "microservices", "denis kolodin"] +tags = ["reviews", "books", "rust", "microservices", "denis kolodin", "it"] +++ +[GoodReads Summary](https://www.goodreads.com/book/show/44079380-hands-on-microservices-with-rust): +A comprehensive guide in developing and deploying high performance +microservices with Rust. + {{ stars(stars=2) }} diff --git a/content/reviews/books/hap-and-leonard-blood-and-lemonade.md b/content/reviews/books/hap-and-leonard-blood-and-lemonade.md index b3901cc..60dd890 100644 --- a/content/reviews/books/hap-and-leonard-blood-and-lemonade.md +++ b/content/reviews/books/hap-and-leonard-blood-and-lemonade.md @@ -2,15 +2,30 @@ title = "Hap and Leonard: Blood and Lemonade - Joe R. Lansdale" date = 2018-01-30 -category = "review" - [taxonomies] -tags = ["books", "en-au", "joe r. lansdale"] +tags = ["books", "joe r. lansdale", "hap and leonard", "reviews", "fiction"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/31921113-blood-and-lemonade): +Hap Collins is a complicated man. He looks like a good ‘ol boy, but his +politics don’t match. After way too many jobs, Hap has discovered what he’s +best at: kicking ass. Vietnam veteran Leonard Pine is even more complicated: +black, Republican, gay—and an occasional arsonist. As childhood friends and +business associates, Hap and Leonard have a gift for the worst kind of +trouble: East Texan trouble. + + + {{ stars(stars=3) }} Another book that came from a Humble Bundle. -It's weird that a book about a couple of disfunctional investigators have absolutely nothing about investigating stuff. I mean, sure, it's a solo book and may fit in the general sense of the series, but for someone coming from outside, it's weird that they try to capture readers by something the series is not. +It's weird that a book about a couple of disfunctional investigators have +absolutely nothing about investigating stuff. I mean, sure, it's a solo book +and may fit in the general sense of the series, but for someone coming from +outside, it's weird that they try to capture readers by something the series +is not. -On the other hand, the stories are well formed and easy to read and paint a long story of the old days in America (which I suppose it's true, 'cause I never lived in the United States, much less in that time). \ No newline at end of file +On the other hand, the stories are well formed and easy to read and paint a +long story of the old days in America (which I suppose it's true, 'cause I +never lived in the United States, much less in that time). diff --git a/content/reviews/books/historia-do-futuro-o-horizonte-do-brasil-no-seculo-xxi.md b/content/reviews/books/historia-do-futuro-o-horizonte-do-brasil-no-seculo-xxi.md index 3f73100..00269f0 100644 --- a/content/reviews/books/historia-do-futuro-o-horizonte-do-brasil-no-seculo-xxi.md +++ b/content/reviews/books/historia-do-futuro-o-horizonte-do-brasil-no-seculo-xxi.md @@ -2,31 +2,84 @@ title = "História do Futuro: O Horizonte do Brasil no Século XXI - Miriam Leitão" date = 2016-04-16 -category = "review" - [taxonomies] -tags = ["books", "en-au", "miriam leitao"] +tags = ["books", "pt-br", "miriam leitao", "reviews"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/25855630-hist-ria-do-futuro): +História do Futuro é um grandioso livro de reportagem em que a jornalista +Míriam Leitão mapeia o território do que está por vir com base em +entrevistas, viagens, análises de dados e depoimentos de especialistas, +depois de três anos de pesquisas. Ela aponta tendências que não podem ser +ignoradas em áreas como meio ambiente e clima, demografia, educação, +economia, política, saúde, energia, agricultura, tecnologia, cidades e mundo. +E adianta que o futuro será implacável para os países que não se prepararem +para ele. + + + {{ stars(stars=2) }} -Quando comecei a ler esse livro, eu realmente gostei: Miriam começa falando sobre as alterações climáticas e a destruição dos recursos naturais, mostrando o que deu de errado e o que foi feito para corrigir esses problemas, de uma forma brilhante. +Quando comecei a ler esse livro, eu realmente gostei: Miriam começa falando +sobre as alterações climáticas e a destruição dos recursos naturais, mostrando +o que deu de errado e o que foi feito para corrigir esses problemas, de uma +forma brilhante. -Na segunda parte é discutido o problema do envelhecimento da população, mostrando que estamos nos aproximando do ponto em que a população brasileira vai começar a se reduzir e a pirâmide de contribuição da previdência está se invertendo. Segurança entra nessa estatística, já que além de menos filhos, a faixa hetaria que entraria no mercado de trabalho acaba morrendo antes de conseguir chegar a isso (e começar a contribuir). +Na segunda parte é discutido o problema do envelhecimento da população, +mostrando que estamos nos aproximando do ponto em que a população brasileira +vai começar a se reduzir e a pirâmide de contribuição da previdência está se +invertendo. Segurança entra nessa estatística, já que além de menos filhos, a +faixa hetaria que entraria no mercado de trabalho acaba morrendo antes de +conseguir chegar a isso (e começar a contribuir). -Terceira parte fala da educação, justamente porque a população está se reduzindo, pedindo para que os trabalhadores do futuro sejam melhores educados e preparados para mudar de situação. +Terceira parte fala da educação, justamente porque a população está se +reduzindo, pedindo para que os trabalhadores do futuro sejam melhores educados +e preparados para mudar de situação. E aí ela fala de economia e a coisa despenca. -Ela comenta os problemas de corrupção no país -- atualizado para até o que se sabia no final de 2015, de uma forma realmente ampla e bem melhor explicado do que qualquer publicação jornalistica por aí -- mas na parte de soluções só são citados os bons e velhos discursos de sempre: desinchar o governo, abrir barreira, reforma tributária, etc, etc, etc. +Ela comenta os problemas de corrupção no país -- atualizado para até o que se +sabia no final de 2015, de uma forma realmente ampla e bem melhor explicado do +que qualquer publicação jornalistica por aí -- mas na parte de soluções só são +citados os bons e velhos discursos de sempre: desinchar o governo, abrir +barreira, reforma tributária, etc, etc, etc. -Acontece que se fosse fácil, já teria sido feito. Enquanto jornalista de economia -- o que garante um conhecimento maior do que a maioria das pessoas -- sair gritando as velhas discussões de sempre sem apresentar uma solução é triste. E soa pior justamente porque ela É jornalista de economia. +Acontece que se fosse fácil, já teria sido feito. Enquanto jornalista de +economia -- o que garante um conhecimento maior do que a maioria das pessoas +-- sair gritando as velhas discussões de sempre sem apresentar uma solução é +triste. E soa pior justamente porque ela É jornalista de economia. -(Não discordo que tem que ser feito, mas ficar simplesmente na discussão sem apresentar soluções, mesmo a longo prazo...) +(Não discordo que tem que ser feito, mas ficar simplesmente na discussão sem +apresentar soluções, mesmo a longo prazo...) -Desse ponto em frente, o castelo de cartas começa a desmoronar. É preciso ensinar as pessoas a poupar, mas é preciso estimular a indústria (se as pessoas estão poupando, a indústria vai vender pra quem?); o mundo está passando para a transformação digital e educação deveria usar esse recurso melhor, apresentando o mundo para as crianças, mas é preciso fazer a indústria ser o maior contribuidor do PIB (minha senhor, se o mundo está virando digital, não deveríamos focar nisso, que é serviço?); as escolas tem que ensinar a pensar, mas é preciso ensinar, desde criança, a poupar (mas se era ensinar a pensar, pra que ter algo específico?); é preciso fazer crescer o PIB com ajuda à indústria, mas o PIB não é uma métrica boa (sem comentários); poluição causa vários problemas de saúde e geração de energia limpa é o futuro, mas é preciso fazer com que a petrobrás tenha uma produção maior (temos que reduzir poluição, mas é preciso investir numa empresa que produz poluição?); quem precisa resolver os problemas do trânsito são as cidades, mas o culpado é o Federal por ter reduzido IPI... E por aí vai. +Desse ponto em frente, o castelo de cartas começa a desmoronar. É preciso +ensinar as pessoas a poupar, mas é preciso estimular a indústria (se as +pessoas estão poupando, a indústria vai vender pra quem?); o mundo está +passando para a transformação digital e educação deveria usar esse recurso +melhor, apresentando o mundo para as crianças, mas é preciso fazer a indústria +ser o maior contribuidor do PIB (minha senhor, se o mundo está virando +digital, não deveríamos focar nisso, que é serviço?); as escolas tem que +ensinar a pensar, mas é preciso ensinar, desde criança, a poupar (mas se era +ensinar a pensar, pra que ter algo específico?); é preciso fazer crescer o PIB +com ajuda à indústria, mas o PIB não é uma métrica boa (sem comentários); +poluição causa vários problemas de saúde e geração de energia limpa é o +futuro, mas é preciso fazer com que a petrobrás tenha uma produção maior +(temos que reduzir poluição, mas é preciso investir numa empresa que produz +poluição?); quem precisa resolver os problemas do trânsito são as cidades, mas +o culpado é o Federal por ter reduzido IPI... E por aí vai. -Não que o livro não seja interessante pela quantidade de informações existentes. O problema é que, numa tentativa de mostrar caminhos para o Brasil do futuro, Miriam acaba sugerindo fazer coisas dispersas. É como perguntar para alguém como chegar num restaurante e essa pessoa dizer que deve-se pegar a direita e a esquerda ao mesmo tempo. Simplesmente, não é possível. +Não que o livro não seja interessante pela quantidade de informações +existentes. O problema é que, numa tentativa de mostrar caminhos para o Brasil +do futuro, Miriam acaba sugerindo fazer coisas dispersas. É como perguntar +para alguém como chegar num restaurante e essa pessoa dizer que deve-se pegar +a direita e a esquerda ao mesmo tempo. Simplesmente, não é possível. -Fora as questões lógicas do conteúdo, existe um problema de edição: vários pontos aparecem com conteúdo repetido, como se a autora tivesse escrito pedaços em momentos diferentes e sequer releu o capítulo novamente para verificar se não há duplicação. +Fora as questões lógicas do conteúdo, existe um problema de edição: vários +pontos aparecem com conteúdo repetido, como se a autora tivesse escrito +pedaços em momentos diferentes e sequer releu o capítulo novamente para +verificar se não há duplicação. -No fim, é um livro interessante pelas informações, mas como sugestões de futuro, parece mais uma tentativa de atirar várias pedras pra ver qual, daqui a alguns anos, atingiu o alvo -- e, as que não atingiram, serão solenemente ignoradas. \ No newline at end of file +No fim, é um livro interessante pelas informações, mas como sugestões de +futuro, parece mais uma tentativa de atirar várias pedras pra ver qual, daqui +a alguns anos, atingiu o alvo -- e, as que não atingiram, serão solenemente +ignoradas. diff --git a/content/reviews/books/horus-rising.md b/content/reviews/books/horus-rising.md index 50ace80..e7d99b9 100644 --- a/content/reviews/books/horus-rising.md +++ b/content/reviews/books/horus-rising.md @@ -3,7 +3,7 @@ title = "Horus Rising - Dan Abnett" date = 2019-10-30 [taxonomies] -tags = ["en-au", "books", "reviews", "warhammer 40000", "dan abnett"] +tags = ["books", "reviews", "warhammer 40000", "dan abnett", "horus heresy", "scifi"] +++ [Goodreads Summary](https://www.goodreads.com/book/show/625603.Horus_Rising): diff --git a/content/reviews/books/how-to-make-mistakes-in-python.md b/content/reviews/books/how-to-make-mistakes-in-python.md index bc07a93..4db7195 100644 --- a/content/reviews/books/how-to-make-mistakes-in-python.md +++ b/content/reviews/books/how-to-make-mistakes-in-python.md @@ -2,13 +2,28 @@ title = "How to Make Mistakes in Python - Mike Pirnat" date = 2017-01-01 -category = "review" - [taxonomies] -tags = ["books", "en-au", "mike pirnat"] +tags = ["books", "mike pirnat", "python", "review", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/28166034-how-to-make-mistakes-in-python): +Even the best programmers make mistakes, and experienced programmer Mike +Pirnat has made his share during 15+ years with Python. Some have been simple +and silly; others were embarrassing and downright costly. In this O’Reilly +report, he dissects some of his most memorable blunders, peeling them back +layer-by-layer to reveal just what went wrong. + + + {{ stars(stars=3) }} -For anyone that works with Python for some time, most of the content of this book is "Hahaha, yeah, I did that too. The good old bad times." And, surely enough, you can't hold yourself nodding when the author mentions that you shouldn't do that. +For anyone that works with Python for some time, most of the content of this +book is "Hahaha, yeah, I did that too. The good old bad times." And, surely +enough, you can't hold yourself nodding when the author mentions that you +shouldn't do that. -I felt it lacked a bit of "this is the right way of doing it", like Uncle Bob did with _Clean Code: A Handbook of Agile Software Craftsmanship_, where he picks a code and starts refactoring till it gets "correct". Most of the time, it's a bunch of code (sometimes, invalid code, but that's minor) and then a simple "don't do that". \ No newline at end of file +I felt it lacked a bit of "this is the right way of doing it", like Uncle Bob +did with _Clean Code: A Handbook of Agile Software Craftsmanship_, where he +picks a code and starts refactoring till it gets "correct". Most of the time, +it's a bunch of code (sometimes, invalid code, but that's minor) and then a +simple "don't do that". diff --git a/content/reviews/books/i-am-legend.md b/content/reviews/books/i-am-legend.md index 299448c..6edefbc 100644 --- a/content/reviews/books/i-am-legend.md +++ b/content/reviews/books/i-am-legend.md @@ -2,13 +2,28 @@ title = "I Am Legend - Richard Matheson" date = 2014-05-20 -category = "review" - [taxonomies] -tags = ["books", "en-au", "richard matheson"] +tags = ["books", "richard matheson", "reviews", "fiction"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/40940649-i-am-legend): +Robert Neville is the last living man on Earth... but he is not alone. Every +other man, woman and child on the planet has become a vampire, and they are +hungry for Neville's blood. + +By day he is the hunter, stalking the undead through the ruins of +civilisation. By night, he barricades himself in his home and prays for the +dawn. + + + {{ stars(stars=4) }} -Sadly, a lot of people may be driven away from the book due the movie -- which follows a very simple plot line. +Sadly, a lot of people may be driven away from the book due the movie -- which +follows a very simple plot line. -But the book does not have a simple plot line. It is complex, twisting and its purpose only shows in the very last line. In that line, the whole story finally clicks; all plots and twists, all descriptions and names, everything clicks. And you stay there, suddenly hit by its plot like a brick hitting you in the side of your face. \ No newline at end of file +But the book does not have a simple plot line. It is complex, twisting and its +purpose only shows in the very last line. In that line, the whole story +finally clicks; all plots and twists, all descriptions and names, everything +clicks. And you stay there, suddenly hit by its plot like a brick hitting you +in the side of your face. diff --git a/content/reviews/books/i-have-no-mouth-and-i-must-scream.md b/content/reviews/books/i-have-no-mouth-and-i-must-scream.md index 0ea4f85..08102fa 100644 --- a/content/reviews/books/i-have-no-mouth-and-i-must-scream.md +++ b/content/reviews/books/i-have-no-mouth-and-i-must-scream.md @@ -2,17 +2,32 @@ title = "I Have No Mouth and I Must Scream - Harlan Ellison" date = 2018-08-23 -category = "review" - [taxonomies] -tags = ["books", "en-au", "harlan ellison"] +tags = ["books", "harlan ellison", "reviews", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/415459.I_Have_No_Mouth_and_I_Must_Scream): +First published in 1967 and re-issued in 1983, I Have No Mouth and I Must +Scream contains seven stories with copyrights ranging from 1958 through 1967. +This edition contains the original introduction by Theodore Sturgeon and the +original foreword by Harlan Ellison, along with a brief update comment by +Ellison that was added in the 1983 edition. Among Ellison's more famous +stories, two consistently noted as among his very best ever are the title +story and the volume's concluding one, Pretty Maggie Moneyeyes. + + + {{ stars(stars=4) }} -For a long time, I've only heard about "Have No Mouth", but never actually read it -- and, to be completely honest, didn't even know it was a story. +For a long time, I've only heard about "Have No Mouth", but never actually +read it -- and, to be completely honest, didn't even know it was a story. And then I got a fiction humble bundle and there it was. -I must say I'm impressed with Harlan writing style. It's easy to read, not too messy and straight -- a thing that reminds me of the way Asimov writes, which allowed me to read whole books in a couple of days. +I must say I'm impressed with Harlan writing style. It's easy to read, not too +messy and straight -- a thing that reminds me of the way Asimov writes, which +allowed me to read whole books in a couple of days. -The stories are all over the place, though: One is scifi, another is hallucinogenic, another is modern fiction... So all tastes should be satiated in the end. \ No newline at end of file +The stories are all over the place, though: One is scifi, another is +hallucinogenic, another is modern fiction... So all tastes should be satiated +in the end. diff --git a/content/reviews/books/imperative-to-functional-programming-succinctly.md b/content/reviews/books/imperative-to-functional-programming-succinctly.md index 32a2bf2..781ce79 100644 --- a/content/reviews/books/imperative-to-functional-programming-succinctly.md +++ b/content/reviews/books/imperative-to-functional-programming-succinctly.md @@ -2,19 +2,40 @@ title = "Imperative to Functional Programming Succinctly - Marc Clifton" date = 2016-12-30 -category = "review" - [taxonomies] -tags = ["books", "en-au", "marc clifton"] +tags = ["books", "marc clifton", "programming", "functional", "c#", "f#", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/23434690-imperative-to-functional-programming-succinctly): +Functional programming is fundamentally different from imperative programming. +As such, it provides a unique approach to solving problems—one that requires +developers to transform how they think about software design and +implementation. With Imperative to Functional Programming Succinctly by Marc +Clifton, you will learn many of the basic concepts involved with functional +programming, such as currying, partial application, function pipelines, +recursion, and continuations. By book's end, you will learn how to combine +functional and imperative programming to get the most out of your solutions. + + + {{ stars(stars=1) }} -I know the "Succinctly" series doesn't go deep into a topic, but this book takes a step further by not even respecting its own title. +I know the "Succinctly" series doesn't go deep into a topic, but this book +takes a step further by not even respecting its own title. The correct title would be "C# to F# Succinctly". -The reason is that there isn't many explanations about "functional programming", in the general sense, in this book. Here, most things are explained in the F# context, which, as the author points, isn't a pure functional language. +The reason is that there isn't many explanations about "functional +programming", in the general sense, in this book. Here, most things are +explained in the F# context, which, as the author points, isn't a pure +functional language. -Also, it goes great lengths to make code unreadable by avoiding proper variable names and using things like "hd" and "tl" (instead of, say, "user" and "remaining_users") and "racc" and "lacc" instead of "sum_right" and "sum_left" (although I could point that this *seems* like a functional programming thing). +Also, it goes great lengths to make code unreadable by avoiding proper +variable names and using things like "hd" and "tl" (instead of, say, "user" +and "remaining_users") and "racc" and "lacc" instead of "sum_right" and +"sum_left" (although I could point that this *seems* like a functional +programming thing). -So, again: Want to use your knowledge of imperative programming to learn functional programming? Sorry, not this book. Know C# and want to learn F#? Then you have something to read. \ No newline at end of file +So, again: Want to use your knowledge of imperative programming to learn +functional programming? Sorry, not this book. Know C# and want to learn F#? +Then you have something to read. diff --git a/content/reviews/books/in-the-beginning-science-faces-god-in-the-book-of-genesis.md b/content/reviews/books/in-the-beginning-science-faces-god-in-the-book-of-genesis.md index 6abdd33..89d82ee 100644 --- a/content/reviews/books/in-the-beginning-science-faces-god-in-the-book-of-genesis.md +++ b/content/reviews/books/in-the-beginning-science-faces-god-in-the-book-of-genesis.md @@ -2,15 +2,36 @@ title = "In the Beginning...: Science Faces God in the Book of Genesis - Isaac Asimov" date = 2018-06-25 -category = "review" - [taxonomies] -tags = ["books", "en-au", "isaac asimov"] +tags = ["books", "isaac asimov", "reviews", "history"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/39341052-in-the-beginning): +In the Beginning: Science Faces God in the Book of Genesis. The beginning of +time. The origin of life. In our Western civilization, there are two +influential accounts of beginnings. One is the biblical account, compiled more +than two thousand years ago by Judean writers who based much of their thinking +on the Babylonian astronomical lore of the day. The other is the account of +modern science, which, in the last century, has slowly built up a coherent +picture of how it all began. Both represent the best thinking of their times, +and in this line-by-line annotation of the first eleven chapters of Genesis, +Isaac Asimov carefully and evenhandedly compares the two accounts, pointing +out where they are similar and where they are different. + + + {{ stars(stars=3) }} -I'm really a fan of Asimov books and I was really eager to read some of his non-fiction books. +I'm really a fan of Asimov books and I was really eager to read some of his +non-fiction books. -On this book, he discusses the Genesis, the first book of the bible. The weird thing is that the introduction makes it seem like he will use the bible as a starting point for science -- the introduction mentions that the people who wrote the bible were not stupid, and they were the most smart people at the time -- so I was expecting it to be more like "they thought this, but now we know this". It wasn't like this; but it was really interesting for pointing what was in the bible and what know at the time. +On this book, he discusses the Genesis, the first book of the bible. The weird +thing is that the introduction makes it seem like he will use the bible as a +starting point for science -- the introduction mentions that the people who +wrote the bible were not stupid, and they were the most smart people at the +time -- so I was expecting it to be more like "they thought this, but now we +know this". It wasn't like this; but it was really interesting for pointing +what was in the bible and what know at the time. -So although it is not a journey to the science, its a really interesting journey to history in the region were the bible was written. +So although it is not a journey to the science, its a really interesting +journey to history in the region were the bible was written. diff --git a/content/reviews/books/instant-backbonejs-application-development.md b/content/reviews/books/instant-backbonejs-application-development.md index 010b2cd..a14435a 100644 --- a/content/reviews/books/instant-backbonejs-application-development.md +++ b/content/reviews/books/instant-backbonejs-application-development.md @@ -2,15 +2,23 @@ title = "Instant Backbone.js Application Development - Thomas Hunter II" date = 2016-04-03 -category = "review" - [taxonomies] -tags = ["books", "en-au", "thomas hunter ii"] +tags = ["books", "thomas hunter ii", "reviews", "javascript", "backbone.js", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18301513-instant-backbone-js-application-development): +Learn something new in an Instant! A short, fast, focused guide delivering +immediate results. + + + {{ stars(stars=1) }} Got this in a promotion, expecting to understand why I should learn backbone. -And the problem is, although the book goes into building a SPA and tells every single step, it severely lacks the "why" you should do such things. Why you should create a "Routes" property on your app; why you have collections AND models, why Backbone can't infer the collections by the models and so on. +And the problem is, although the book goes into building a SPA and tells every +single step, it severely lacks the "why" you should do such things. Why you +should create a "Routes" property on your app; why you have collections AND +models, why Backbone can't infer the collections by the models and so on. -In the end, I think I learnt more about LoDash than Backbone. \ No newline at end of file +In the end, I think I learnt more about LoDash than Backbone. diff --git a/content/reviews/books/ipad-productivity-essentials-the-definitive-guide-to-getting-more-productive-with-your-ipad.md b/content/reviews/books/ipad-productivity-essentials-the-definitive-guide-to-getting-more-productive-with-your-ipad.md index 34bb69f..d2d723b 100644 --- a/content/reviews/books/ipad-productivity-essentials-the-definitive-guide-to-getting-more-productive-with-your-ipad.md +++ b/content/reviews/books/ipad-productivity-essentials-the-definitive-guide-to-getting-more-productive-with-your-ipad.md @@ -1,18 +1,38 @@ +++ -title = "iPad® Productivity Essentials: The Definitive Guide to Getting More Productive with your iPad - Christopher J. Lee" +title = "iPad Productivity Essentials: The Definitive Guide to Getting More Productive with your iPad - Christopher J. Lee" date = 2015-03-21 -category = "review" - [taxonomies] -tags = ["books", "en-au", "christopher j. lee"] +tags = ["books", "christopher j. lee", "ipad", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/24440122-ipad-productivity-essentials): +You have your iPad, now what? You could continue to use your tablet as an +excellent web surfing tool. You could also use it to play one of the many, +many games out on the App Store. Or, you could simply turn it over to your +spouse or your kid(s) for their enjoyment. I suggest a different path, a path +that will keep your iPad in your hands, at work…a path that will put you on +the road towards increased productivity! + + + {{ stars(stars=1) }} **Easy way to describe this: lazy** -You know, for a book with a subtitle of "Get efficient with your iPad, Evernote and GTD" (or, at least, that's what my edition says in the cover), I really expect something more around the lines of "Here is GTD and here is how you do this GTD thing with your iPad, and here is how you do this GTD thing inside Evernote". Instead, the book goes talking about apps that two months from now will not make sense, which are completely unrelated to each other (so good look trying to mix them together and get something meaningful), and which, most of the time, have nothing to do GTD or Evernote. +You know, for a book with a subtitle of "Get efficient with your iPad, +Evernote and GTD" (or, at least, that's what my edition says in the cover), I +really expect something more around the lines of "Here is GTD and here is how +you do this GTD thing with your iPad, and here is how you do this GTD thing +inside Evernote". Instead, the book goes talking about apps that two months +from now will not make sense, which are completely unrelated to each other (so +good look trying to mix them together and get something meaningful), and +which, most of the time, have nothing to do GTD or Evernote. -Also, there are a few quirks in the edition that really annoyed me: there some marks around the text that seems there was some editor marking down corrections to be made, but instead of checking those, the author decided to publish the book with the marks instead of the final product. +Also, there are a few quirks in the edition that really annoyed me: there some +marks around the text that seems there was some editor marking down +corrections to be made, but instead of checking those, the author decided to +publish the book with the marks instead of the final product. -In the end, it feels like a bunch of blog posts tied together instead of something really targeted towards GTD and Evernote. \ No newline at end of file +In the end, it feels like a bunch of blog posts tied together instead of +something really targeted towards GTD and Evernote. diff --git a/content/reviews/books/javascript-testing-beginners-guide.md b/content/reviews/books/javascript-testing-beginners-guide.md index a3a5079..f468b01 100644 --- a/content/reviews/books/javascript-testing-beginners-guide.md +++ b/content/reviews/books/javascript-testing-beginners-guide.md @@ -2,17 +2,48 @@ title = "JavaScript Testing Beginner's Guide - Liang Yuxian Eugene" date = 2015-09-10 -category = "review" - [taxonomies] -tags = ["books", "en-au", "liang yuxian eugene"] +tags = ["books", "liang yuxian eugene", "reviews", "javascript", "tests", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/9272372-javascript-testing-beginner-s-guide): +This book is organized such that only the most essential information is +provided to you in each chapter so as to maximize your learning. Examples and +tutorials are given in an easy to follow, step-by-step manner so that you can +see how the testing process is being carried out and how the code is being +written. The source code also contains detailed explanation so that you know +what the code is doing. Multiple screenshots are used in places that matter so +that you have a visual sense of what is happening. Beginner JavaScript +developers looking for essential ways to write, test, and debug JavaScript for +different purposes and situations. + + + {{ stars(stars=1) }} -Let me start this by saying that I really liked the structure of the book. For each chapter, there is an explanation of what will be covered; a "call for action" which shows the code and then describes, step by step, what is going on; a further explanation on when running said code; and, finally, some pointers on where to go forward. +Let me start this by saying that I really liked the structure of the book. For +each chapter, there is an explanation of what will be covered; a "call for +action" which shows the code and then describes, step by step, what is going +on; a further explanation on when running said code; and, finally, some +pointers on where to go forward. -That being said, this is a mess of a book. The kindle version is completely mangled on the source code. Indentation is completely wrong, which makes the code hard to read; the code is full of stupid mistakes (like having an object and trying to get it again with `getElementById(element.id)`); and, generally, it's pure bad code (like raising an exception inside a try/catch just to catch it afterwards). Not only that, but the book goes incredible lengths to explain JavaScript, what are unit tests and such and, just in the last chapter, it finally explains JavaScript Testing. +That being said, this is a mess of a book. The kindle version is completely +mangled on the source code. Indentation is completely wrong, which makes the +code hard to read; the code is full of stupid mistakes (like having an object +and trying to get it again with `getElementById(element.id)`); and, generally, +it's pure bad code (like raising an exception inside a try/catch just to catch +it afterwards). Not only that, but the book goes incredible lengths to explain +JavaScript, what are unit tests and such and, just in the last chapter, it +finally explains JavaScript Testing. -That wouldn't be so bad if it was a recent book. But it's a book from 2010, with no further editions, and a lot has changed in the JavaScript landscape in those last 5 years. New frameworks appeared, new tools are here, JavaScript is not client side only anymore... The list goes on and on. Heck, the author goes lengths to explain how to test in IE because it's the most used browser at the time! +That wouldn't be so bad if it was a recent book. But it's a book from 2010, +with no further editions, and a lot has changed in the JavaScript landscape in +those last 5 years. New frameworks appeared, new tools are here, JavaScript is +not client side only anymore... The list goes on and on. Heck, the author goes +lengths to explain how to test in IE because it's the most used browser at the +time! -Honestly, stay away from this book. Get a book about JavaScript. Get a book about testing. Pick one of the JavaScript testing frameworks around (I know at least 5), read its documentation and you'll be in a better place than reading this. \ No newline at end of file +Honestly, stay away from this book. Get a book about JavaScript. Get a book +about testing. Pick one of the JavaScript testing frameworks around (I know at +least 5), read its documentation and you'll be in a better place than reading +this. diff --git a/content/reviews/books/just-a-geek-unflinchingly-honest-tales-of-the-search-for-life-love-and-fulfillment-beyond-the-starship-enterprise.md b/content/reviews/books/just-a-geek-unflinchingly-honest-tales-of-the-search-for-life-love-and-fulfillment-beyond-the-starship-enterprise.md index fe82c13..9a2925a 100644 --- a/content/reviews/books/just-a-geek-unflinchingly-honest-tales-of-the-search-for-life-love-and-fulfillment-beyond-the-starship-enterprise.md +++ b/content/reviews/books/just-a-geek-unflinchingly-honest-tales-of-the-search-for-life-love-and-fulfillment-beyond-the-starship-enterprise.md @@ -2,19 +2,61 @@ title = "Just a Geek: Unflinchingly honest tales of the search for life, love, and fulfillment beyond the Starship Enterprise - Wil Wheaton" date = 2015-01-31 -category = "review" - [taxonomies] -tags = ["books", "en-au", "wil wheaton"] +tags = ["books", "wil wheaton", "reviews", "geek", "star trek"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/65692.Just_a_Geek): +Wil Wheaton has never been one to take the conventional path to success. +Despite early stardom through his childhood role in the motion picture "Stand +By Me," and growing up on television as Wesley Crusher on "Star Trek: The +Next Generation," Wil left Hollywood in pursuit of happiness, purpose, and a +viable means of paying the bills. In the oddest of places, Topeka, Kansas, +Wil discovered that despite his claims to fame, he was at heart "Just a +Geek." In this bestselling book, Wil shares his deeply personal and difficult +journey to find himself. You'll understand the rigors, and joys, of Wil's +rediscovering of himself, as he comes to terms with what it means to be +famous, or, ironically, famous for once having been famous. Writing with +honesty and disarming humanity, Wil touches on the frustrations associated +with his acting career, his inability to distance himself from Ensign Crusher +in the public's eyes, the launch of his incredibly successful web site, +wilwheaton.net, and the joy he's found in writing. Through all of this, Wil +shares the ups and downs he encountered along the journey, along with the +support and love he discovered from his friends and family. The stories in +"Just a Geek" include: Wil's plunge from teen star to struggling actor, +discovering the joys of HTML, blogging, Linux, and web design, the struggle +between Wesley Crusher, Starfleet ensign, and Wil Wheaton, author and +blogger, gut-wrenching reactions to the 9-11 disaster, moving tales of Wil's +relationships with his wife, step-children, and extended family, and the +transition from a B-list actor to an A-list author. + + + {{ stars(stars=4) }} -Wil Wheaton is a weird character. Some of this acting I find bad, but some are incredible natural (compare his early Wesley Crusher acting with his late The Guild acting. Also, assorted Big Bang Theory episodes). +Wil Wheaton is a weird character. Some of this acting I find bad, but some are +incredible natural (compare his early Wesley Crusher acting with his late The +Guild acting. Also, assorted Big Bang Theory episodes). -On the other hand, writing seems to be his strongest point -- something that we reckons himself in this book. +On the other hand, writing seems to be his strongest point -- something that +we reckons himself in this book. -In "Just a Geek", Wheaton collects some of his blog posts from wilwheaton.net and tells the story behind them. In a way, it's the reverse of _Ghost Rider: Travels on the Healing Road_: Instead of telling what was happening with hidden emotions and then telling the truth in other media (in "Ghost Rider", it's Neil letters), here Wheaton sounds like everything is going fine in the blog posts -- at least, in the first ones -- and tells what was wrong in the book itself. +In "Just a Geek", Wheaton collects some of his blog posts from wilwheaton.net +and tells the story behind them. In a way, it's the reverse of _Ghost Rider: +Travels on the Healing Road_: Instead of telling what was happening with +hidden emotions and then telling the truth in other media (in "Ghost Rider", +it's Neil letters), here Wheaton sounds like everything is going fine in the +blog posts -- at least, in the first ones -- and tells what was wrong in the +book itself. -I feel like an idiot describing this, because it sounds too much like some marketing/paid content, but the book goes from the child actor in Star Trek: The Next Generation era to his internet celebrity point (although it doesn't go into the internet-video era, with The Guild) and Wheaton admits all his errors and how he "found himself" (anyone who had to go through this road can related to his story). +I feel like an idiot describing this, because it sounds too much like some +marketing/paid content, but the book goes from the child actor in Star Trek: +The Next Generation era to his internet celebrity point (although it doesn't +go into the internet-video era, with The Guild) and Wheaton admits all his +errors and how he "found himself" (anyone who had to go through this road can +related to his story). -It's nice to read, even to get some idea behind TNG. It's direct, with Wheaton telling every time he got pissed with himself. And, in the end, it's a very well written book, although there is a lot of content coming from other sources. \ No newline at end of file +It's nice to read, even to get some idea behind TNG. It's direct, with Wheaton +telling every time he got pissed with himself. And, in the end, it's a very +well written book, although there is a lot of content coming from other +sources. diff --git a/content/reviews/books/land-of-lisp-learn-to-program-in-lisp-one-game-at-a-time.md b/content/reviews/books/land-of-lisp-learn-to-program-in-lisp-one-game-at-a-time.md index ffa672e..dfe959d 100644 --- a/content/reviews/books/land-of-lisp-learn-to-program-in-lisp-one-game-at-a-time.md +++ b/content/reviews/books/land-of-lisp-learn-to-program-in-lisp-one-game-at-a-time.md @@ -2,19 +2,43 @@ title = "Land of Lisp: Learn to Program in Lisp, One Game at a Time! - Conrad Barski" date = 2017-03-16 -category = "review" - [taxonomies] -tags = ["books", "en-au", "conrad barski"] +tags = ["books", "conrad barski", "lisp", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/6905041-land-of-lisp): +Lisp is a uniquely powerful programming language that, despite its academic reputation, is actually very practical. Land of Lisp brings the language into the real world, teaching Lisp by showing readers how to write several complete Lisp-based games, including a text adventure, an evolution simulation, and a robot battle. While building these games, readers learn the core concepts of Lisp programming, such as data types, recursion, input/output, object-oriented programming, and macros. And thanks to the power of Lisp, the code is short. Rather than bogging things down with reference information that is easily found online, Land of Lisp focuses on using Lisp for real programming. The book is filled with the author Conrad Barski's famous Lisp cartoons, featuring the Lisp alien and other zany characters. + + + + {{ stars(stars=3) }} (Once again, ignoring the language itself to focus on the book). -Lisp is one hell of a language. Lots of things that are getting traction today already exist in Lisp for a long time. And, still, Lisp is not a common language. And this book shows why. +Lisp is one hell of a language. Lots of things that are getting traction today +already exist in Lisp for a long time. And, still, Lisp is not a common +language. And this book shows why. -Just before reaching 1/4 of the book, there was a little piece of code that had nothing less than six "close parenthesis" in it. Just to have an idea of how bad it is, one of my friends that know Lisp inside and out rewrote the same piece of code using two new functions and hell, it was a lot easier to read -- simple because Lisp must be read from right to left, which most written languages use the other way around and reducing the closing parenthesis by moving pieces of code to other functions really does help. +Just before reaching 1/4 of the book, there was a little piece of code that +had nothing less than six "close parenthesis" in it. Just to have an idea of +how bad it is, one of my friends that know Lisp inside and out rewrote the +same piece of code using two new functions and hell, it was a lot easier to +read -- simple because Lisp must be read from right to left, which most +written languages use the other way around and reducing the closing +parenthesis by moving pieces of code to other functions really does help. -The book also fails in a lot of places: There is the constant abuse of global variables, which breaks the idea of functional programming, one of the pillars of the language; the whole code focus on the REPL and nowhere it talks about using an external editor and running the code, although in the very end a magical "load" appears, out of the blue; there is some serious lack of contextualization about concepts: things are simply thrown out and *then* explained (there is a piece about minimax which the author simply explains the code after showing it and, in the next chapter, he finally explains the minimax concept, only to tell that the code could be "fixed" to follow it in only 23 lines -- no shit, Sherlock, you wrote half of it without ever explaining *why* you were writing it). +The book also fails in a lot of places: There is the constant abuse of global +variables, which breaks the idea of functional programming, one of the pillars +of the language; the whole code focus on the REPL and nowhere it talks about +using an external editor and running the code, although in the very end a +magical "load" appears, out of the blue; there is some serious lack of +contextualization about concepts: things are simply thrown out and *then* +explained (there is a piece about minimax which the author simply explains the +code after showing it and, in the next chapter, he finally explains the +minimax concept, only to tell that the code could be "fixed" to follow it in +only 23 lines -- no shit, Sherlock, you wrote half of it without ever +explaining *why* you were writing it). -In the end, it's not a "oh so terrible" book, but it could really use some editing help. \ No newline at end of file +In the end, it's not a "oh so terrible" book, but it could really use some +editing help. diff --git a/content/reviews/books/learn-you-a-haskell-for-great-good.md b/content/reviews/books/learn-you-a-haskell-for-great-good.md index f0726f7..1d579e7 100644 --- a/content/reviews/books/learn-you-a-haskell-for-great-good.md +++ b/content/reviews/books/learn-you-a-haskell-for-great-good.md @@ -2,11 +2,24 @@ title = "Learn You a Haskell for Great Good! - Miran Lipovača" date = 2018-11-23 -category = "review" - [taxonomies] -tags = ["books", "en-au", "miran lipovaca", "haskell"] +tags = ["books", "miran lipovaca", "haskell", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/6593810-learn-you-a-haskell-for-great-good): +Learn You a Haskell for Great Good! is a fun, illustrated guide to learning +Haskell, a functional programming language that's growing in popularity. Learn +You a Haskell for Great Good! introduces programmers familiar with imperative +languages (such as C++, Java, or Python) to the unique aspects of functional +programming. Packed with jokes, pop culture references, and the author's own +hilarious artwork, Learn You a Haskell for Great Good! eases the learning +curve of this complex language, and is a perfect starting point for any +programmer looking to expand his or her horizons. The well-known web tutorial +on which this book is based is widely regarded as the best way for beginners +to learn Haskell, and receives over 30,000 unique visitors monthly. + + + {{ stars(stars=2) }} I have mixed feelings about this book. diff --git a/content/reviews/books/learning-ecmascript-6.md b/content/reviews/books/learning-ecmascript-6.md index f498759..21752d6 100644 --- a/content/reviews/books/learning-ecmascript-6.md +++ b/content/reviews/books/learning-ecmascript-6.md @@ -2,19 +2,40 @@ title = "Learning ECMAScript 6 - Narayan Prusty" date = 2016-02-18 -category = "review" - [taxonomies] -tags = ["books", "en-au", "narayan prusty"] +tags = ["books", "narayan prusty", "reviews", "javascript", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/26236031-learning-ecmascript-6): +About This Book Learn a powerful approach to writing object-oriented +JavaScript code using ES6 Create and use ES6 modules to learn to write smart, +modularized JavaScript code The book will take you step-by-step through a wide +array of examples, giving you tips on how to make the best use of the latest +ES6 features Who This Book Is For + + + {{ stars(stars=2) }} -ECMAScript 6 is the new JavaScript, and I'm just saying this in case you're wondering why one would read this book. +ECMAScript 6 is the new JavaScript, and I'm just saying this in case you're +wondering why one would read this book. -There are a few niceties in JavaScript 6 that would make lives easier. I read the book looking for those niceties. And it does its job. Poorly. +There are a few niceties in JavaScript 6 that would make lives easier. I read +the book looking for those niceties. And it does its job. Poorly. -Thing is, the first examples are good (not great, good), and then it seems there are some components the author didn't really quite grasped -- like proxies -- and threw examples of things without them. In the case of proxies, the author created proxies that replicate the normal behaviour of objects and after reading it, you'll keep wondering *why* you should use them, as they do nothing different from the default. +Thing is, the first examples are good (not great, good), and then it seems +there are some components the author didn't really quite grasped -- like +proxies -- and threw examples of things without them. In the case of proxies, +the author created proxies that replicate the normal behaviour of objects and +after reading it, you'll keep wondering *why* you should use them, as they do +nothing different from the default. -Also, broken English. I'll be the first saying that I'm not the most impressive writer in the English language, but hell, some sentences really hurt. "we will be comparing" is one of those cases. And you'll find plenty of them. Plenty of "that is", plenty "therefore" and things like that just make the text tiring to read -- and it's not even a long read, just about 200 pages. +Also, broken English. I'll be the first saying that I'm not the most +impressive writer in the English language, but hell, some sentences really +hurt. "we will be comparing" is one of those cases. And you'll find plenty of +them. Plenty of "that is", plenty "therefore" and things like that just make +the text tiring to read -- and it's not even a long read, just about 200 +pages. -It's a book that may give you some insights about what's new in JavaScript, but falls short delivering its message. \ No newline at end of file +It's a book that may give you some insights about what's new in JavaScript, +but falls short delivering its message. diff --git a/content/reviews/books/learning-ionic-build-real-time-and-hybrid-mobile-applications-with-ionic.md b/content/reviews/books/learning-ionic-build-real-time-and-hybrid-mobile-applications-with-ionic.md index ea47bc5..022a3d1 100644 --- a/content/reviews/books/learning-ionic-build-real-time-and-hybrid-mobile-applications-with-ionic.md +++ b/content/reviews/books/learning-ionic-build-real-time-and-hybrid-mobile-applications-with-ionic.md @@ -5,12 +5,33 @@ date = 2016-02-04 category = "review" [taxonomies] -tags = ["books", "en-au", "arvind ravulavaru"] +tags = ["books", "arvind ravulavaru", "mobile", "ionic", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/26080566-learning-ionic---build-real-time-and-hybrid-mobile-applications-with-ion): +Key Features Create hybrid mobile applications by combining the capabilities +of Ionic, Cordova, and AngularJS Reduce the time to market your application +using Ionic, that helps in rapid application development Detailed code +examples and explanations, helping you get up and running with Ionic quickly +and easily Book Description + + + + {{ stars(stars=4) }} -I must say, I was really surprised by this book. Not only it goes a great length to explain things about Angular (the base for Ionic), but builds two applications from start to end, connects to other services and also explains how to publish your application. +I must say, I was really surprised by this book. Not only it goes a great +length to explain things about Angular (the base for Ionic), but builds +two applications from start to end, connects to other services and also +explains how to publish your application. -But (and there is always a "but") I felt some things lacking. For example, the author says that he prefers to use grunt instead of the default ionic tool, but after that, he *only* uses the ionic tool; there are some things wrong with the book (why I already submitted as an errata for it); there is very little mention on how to deal with different rotations; and the gravest problem of all, in my opinion: There are absolutely no tests. At all. Not even a mention on how to test your Ionic app. +But (and there is always a "but") I felt some things lacking. For example, the +author says that he prefers to use grunt instead of the default ionic tool, +but after that, he *only* uses the ionic tool; there are some things wrong +with the book (why I already submitted as an errata for it); there is very +little mention on how to deal with different rotations; and the gravest +problem of all, in my opinion: There are absolutely no tests. At all. Not even +a mention on how to test your Ionic app. -Other that those problems (which are really minor, related to the amount of information), it is really a good book to start working with Ionic apps. \ No newline at end of file +Other that those problems (which are really minor, related to the amount of +information), it is really a good book to start working with Ionic apps. diff --git a/content/reviews/books/learning-java.md b/content/reviews/books/learning-java.md index 0f8bb38..c1eb263 100644 --- a/content/reviews/books/learning-java.md +++ b/content/reviews/books/learning-java.md @@ -2,17 +2,49 @@ title = "Learning Java - Patrick Niemeyer" date = 2018-08-03 -category = "review" - [taxonomies] -tags = ["books", "en-au", "patrick niemeyer"] +tags = ["books", "patrick niemeyer", "reviews", "java", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/665984.Learning_Java): +Version 5.0 of the Java 2 Standard Edition SDK is the most important upgrade +since Java first appeared a decade ago. With Java 5.0, you'll not only find +substantial changes in the platform, but to the language itself-something that +developers of Java took five years to complete. The main goal of Java 5.0 is +to make it easier for you to develop safe, powerful code, but none of these +improvements makes Java any easier to learn, even if you've programmed with +Java for years. And that means our bestselling hands-on tutorial takes on even +greater significance."Learning Java" is the most widely sought introduction to +the programming language that's changed the way we think about computing. Our +updated third edition takes an objective, no-nonsense approach to the new +features in Java 5.0, some of which are drastically different from the way +things were done in any previous versions. The most essential change is the +addition of "generics," a feature that allows developers to write, test, and +deploy code once, and then reuse the code again and again for different data +types. The beauty of generics is that more problems will be caught during +development, and "Learning Java" will show you exactly how it's done.Java 5.0 +also adds more than 1,000 new classes to the Java library. That means 1,000 +new things you can do without having to program it in yourself. That's a huge +change. With our book's practical examples, you'll come up to speed quickly on +this and other new features such as loops and threads. The new edition also +includes an introduction to Eclipse, the open source IDE that is growing in +popularity. "Learning Java," 3rd Edition addresses all of the important uses +of Java, such as web applications, servlets, and XML that are increasingly +driving enterprise applications. + + + {{ stars(stars=2) }} -I once said that it's not just the matter of wanting to learn something, there is also the matter of wanting to *teach*. +I once said that it's not just the matter of wanting to learn something, there +is also the matter of wanting to *teach*. The problem here is that the book doesn't seem interested in the second. -I mean, sure, it's nice that you go through *all* the classes, but... is it necessary? Is this teaching? Not to me. +I mean, sure, it's nice that you go through *all* the classes, but... is it +necessary? Is this teaching? Not to me. -Either focus on how things work and how to pick things, but going over and over and over over *everything* is tiring and not helpful. Not to mention there is a lot of things said twice (or even more), which seems focused on making the book bigger, instead of making things clearer. \ No newline at end of file +Either focus on how things work and how to pick things, but going over and +over and over over *everything* is tiring and not helpful. Not to mention +there is a lot of things said twice (or even more), which seems focused on +making the book bigger, instead of making things clearer. diff --git a/content/reviews/books/less-web-development-essentials.md b/content/reviews/books/less-web-development-essentials.md index 7dc4470..de78551 100644 --- a/content/reviews/books/less-web-development-essentials.md +++ b/content/reviews/books/less-web-development-essentials.md @@ -2,15 +2,35 @@ title = "Less Web Development Essentials - Bass Jobsen" date = 2016-08-02 -category = "review" - [taxonomies] -tags = ["books", "en-au", "bass jobsen"] +tags = ["books", "bass jobsen", "reviews", "css", "less", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/22130122-less-web-development-essentials): +Written in a practical and concise manner, this book is a crash-course in +teaching you the fundamental concepts of Less with real-life examples and +problems. If you use CSS(3) in your web development tasks and would love to +learn how to create maintainable and reusable code with Less, this book is +ideal for you. Although you need to have some experience in web development, +even beginners will find that this book is useful. + + + + {{ stars(stars=2) }} -Less is a compiler for CSS. Why do I feel I need to start a review with that? Because this book focuses a lot more on CSS than Less. Actually, I may have learnt more about CSS than what it was expected to learn. There is nothing wrong talking more about the base technology when the piece you're talking about is built on it, but when you talk a lot more about the first and not the second, you have to seriously reconsider your book title. +Less is a compiler for CSS. Why do I feel I need to start a review with that? +Because this book focuses a lot more on CSS than Less. Actually, I may have +learnt more about CSS than what it was expected to learn. There is nothing +wrong talking more about the base technology when the piece you're talking +about is built on it, but when you talk a lot more about the first and not the +second, you have to seriously reconsider your book title. -Another thing that annoys me is when the author keeps talking about the examples outside the book. "Check the examples which you can download in the previous URL" is lazy explanation. Instead of building knowledge blocks and then expand over them, the book uses the lazy escape of not telling you anything and expecting yo to read things somewhere else. +Another thing that annoys me is when the author keeps talking about the +examples outside the book. "Check the examples which you can download in the +previous URL" is lazy explanation. Instead of building knowledge blocks and +then expand over them, the book uses the lazy escape of not telling you +anything and expecting yo to read things somewhere else. -In the end, it's a nice book to learn a thing or two about modern CSS, but barely something good about Less. \ No newline at end of file +In the end, it's a nice book to learn a thing or two about modern CSS, but +barely something good about Less. diff --git a/content/reviews/books/linux-shell-scripting-cookbook.md b/content/reviews/books/linux-shell-scripting-cookbook.md index f14efb4..202cfa7 100644 --- a/content/reviews/books/linux-shell-scripting-cookbook.md +++ b/content/reviews/books/linux-shell-scripting-cookbook.md @@ -2,23 +2,64 @@ title = "Linux Shell Scripting Cookbook - Shantanu Tushar" date = 2016-01-13 -category = "review" - [taxonomies] -tags = ["books", "en-au", "shantanu tushar"] +tags = ["books", "shantanu tushar", "reviews", "it", "shell script"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/10370134-linux-shell-scripting-cookbook): +This cookbook is for beginners or intermediate Linux users who want to master +writing Bash shell scripts. Intermediate/advanced users, system +administrators, developers, and programmers can use it as a reference when +they face problems while coding. Each recipe contains step-by-step +instructions about everything necessary to execute a particular task. The book +is designed so that beginners can read it from start to end while advanced +users can just open it at any chapter and start following the recipes as a +reference. It covers most of the commands on Linux with a variety of use cases +accompanied by plenty of examples and guides you on implementing some of the +commonest Linux commands with recipes that handle operations or properties +related to files like searching and mining inside a file with grep. It also +shows how utilities like sed, awk, grep, and cut can be combined to solve text +processing problems. The focus is on saving time by automating activities with +a few lines of script. + + + {{ stars(stars=2) }} -I don't know why, but when I saw the title, I expected to be a book only about bash. Bash is a shell for *nix based systems and, as VIM, is one of the apps you can use for 10 years and, after reading something about it, you find something completely new. +I don't know why, but when I saw the title, I expected to be a book only about +bash. Bash is a shell for *nix based systems and, as VIM, is one of the apps +you can use for 10 years and, after reading something about it, you find +something completely new. -Thing is, this is not just about bash. This book is about tools in the GNU system that can help write shell scripts. And even if you're pissed about Stallman asking to call the system GNU/Linux, this *is* about GNU tools: tr, expect, find... All GNU tools. +Thing is, this is not just about bash. This book is about tools in the GNU +system that can help write shell scripts. And even if you're pissed about +Stallman asking to call the system GNU/Linux, this *is* about GNU tools: tr, +expect, find... All GNU tools. So "GNU Shell Scripting Cookbook" would be a more appropriate title. -About the content itself... It's mostly a miss than a hit. Some things are some wrong it hurts (Git does *not* add a `.git` directory inside every directory) and some are so utterly stupid to the point of being dangerous (you don't need root to chown a file!). Some points are so strange, they seem like the authors used a GNU/Linux for only two months and decided to write a book about it. +About the content itself... It's mostly a miss than a hit. Some things are +some wrong it hurts (Git does *not* add a `.git` directory inside every +directory, it creates one at the base directory of the project) and some are +so utterly stupid to the point of being dangerous (you don't need root to +chown a file!). Some points are so strange, they seem like the authors used a +GNU/Linux for only two months and decided to write a book about it. -The book have two authors and it shows. Lots of repeated information, some things not building on things already said (really guys? Not matching pipe with stdin/stdout redirection?) will give you the impression that they never spoke about the book or had a roadmap for it. And there is a shitton of "as follows" (seriously, you'll get sick of reading "as follows" over the book). It says in the cover that, besides the two authors, there were at least 5 reviewers. But it seems none of them actually read the book -- and I'm not talking about easy things to find in a 1 minute Google search (like the git thing), but things like "this 'as follows' is getting through my nerves, you're using it every-fucking-where". +The book have two authors and it shows. Lots of repeated information, some +things not building on things already said (really guys? Not matching pipe +with stdin/stdout redirection?) will give you the impression that they never +spoke about the book or had a roadmap for it. And there is a shitton of "as +follows" (seriously, you'll get sick of reading "as follows" over the book). +It says in the cover that, besides the two authors, there were at least 5 +reviewers. But it seems none of them actually read the book -- and I'm not +talking about easy things to find in a 1 minute Google search (like the git +thing), but things like "this 'as follows' is getting through my nerves, +you're using it every-fucking-where". -The content gets better in the end, when it gets over the "teaching phase", but you'll still have the bad taste of things wrong from the previous chapters. +The content gets better in the end, when it gets over the "teaching phase", +but you'll still have the bad taste of things wrong from the previous +chapters. -So, basically, the book tries to cater to two different audiences -- the beginner and the master -- and doesn't seem to be able to provide a good content for any. \ No newline at end of file +So, basically, the book tries to cater to two different audiences -- the +beginner and the master -- and doesn't seem to be able to provide a good +content for any. diff --git a/content/reviews/books/mastering-emacs.md b/content/reviews/books/mastering-emacs.md index 6e6a4f8..d44643f 100644 --- a/content/reviews/books/mastering-emacs.md +++ b/content/reviews/books/mastering-emacs.md @@ -3,7 +3,7 @@ title = "Mastering Emacs, Mickey Petersen" date = 2019-11-18 [taxonomies] -tags = ["en-au", "books", "reviews", "emacs", "mickey petersen"] +tags = ["books", "reviews", "emacs", "mickey petersen", "it"] +++ [GoodReads summary](https://www.goodreads.com/book/show/25587882-mastering-emacs): diff --git a/content/reviews/books/mastering-javascript-design-patterns-essential-solutions-for-effective-javascript-web-design.md b/content/reviews/books/mastering-javascript-design-patterns-essential-solutions-for-effective-javascript-web-design.md index 2a0e336..5dc3691 100644 --- a/content/reviews/books/mastering-javascript-design-patterns-essential-solutions-for-effective-javascript-web-design.md +++ b/content/reviews/books/mastering-javascript-design-patterns-essential-solutions-for-effective-javascript-web-design.md @@ -2,23 +2,53 @@ title = "Mastering JavaScript Design Patterns - Essential Solutions for Effective JavaScript Web Design - Simon Timms" date = 2016-03-12 -category = "review" - [taxonomies] -tags = ["books", "en-au", "simon timms"] +tags = ["books", "simon timms", "reviews", "javascript", "design patterns", "it"] +++ -{{ stars(stars=2) }} - -With a book named "Master JavaScript Design Patterns", I was expecting something about some JavaScript common patterns, like subscribing and generating events, proper way of transversing structures and such. -But nope. +[GoodReads Summary](https://www.goodreads.com/book/show/23847040-mastering-javascript-design-patterns---essential-solutions-for-effective): +Enhance your JavaScript code with this essential collection of design +patterns. Discover an extensive range of techniques and strategies to +successfully tackle complex JavaScript development problems and put them into +practice by following detailed examples that demonstrate each design pattern +at its most effective. Dive deeper into JavaScript and master these powerful +design patterns for an innovative and cutting-edge approach to JavaScript that +meets the demands of modern web development. -The book starts with the classical design patterns from the Gang of Four, which doesn't seem so bad if the book was named "Learning Design Patterns with JavaScript", in a way to make learning the design patterns more streamlined for people who already know JavaScript. But, then again, things fall apart, with the Observer pattern being designed with a list of callbacks in a structured, instead of creating a real event -- something, again, really common in JavaScript. + -Not only that, but some stuff seems really off. Like explaining lazy evaluation -- something only ES6 has -- with... lists. Yup, lazy evaluation, for the book, means adding things in a list only when you need to remove things from the list. It would make so much more sense if the author jumped into the ES6 bandwagon for this and explained the "yield" command... but no, he had to write some lazy text. +{{ stars(stars=2) }} -The fact that all examples are based on Game of Thrones -- with all being based on things that happen in Westeros -- don't make it funny or interesting. Worse, none of the examples are related, so the author just keeps jumping between weird scenarios to explain the "patterns". +With a book named "Master JavaScript Design Patterns", I was expecting +something about some JavaScript common patterns, like subscribing and +generating events, proper way of transversing structures and such. -Even when you throw the JavaScript away and decide to read it to learn some design patterns, you waste your time. Some designs, mostly the MV*, are hastily described and just superficially analyzed. +But nope. -It really starts a bit off -- again, if it was "Learning Design Patterns with JavaScript", it would be almost perfect -- and then goes downhill by some lazy writing and wrong assumptions. \ No newline at end of file +The book starts with the classical design patterns from the Gang of Four, +which doesn't seem so bad if the book was named "Learning Design Patterns with +JavaScript", in a way to make learning the design patterns more streamlined +for people who already know JavaScript. But, then again, things fall apart, +with the Observer pattern being designed with a list of callbacks in a +structured, instead of creating a real event -- something, again, really +common in JavaScript. + +Not only that, but some stuff seems really off. Like explaining lazy +evaluation -- something only ES6 has -- with... lists. Yup, lazy evaluation, +for the book, means adding things in a list only when you need to remove +things from the list. It would make so much more sense if the author jumped +into the ES6 bandwagon for this and explained the "yield" command... but no, +he had to write some lazy text. + +The fact that all examples are based on Game of Thrones -- with all being +based on things that happen in Westeros -- don't make it funny or interesting. +Worse, none of the examples are related, so the author just keeps jumping +between weird scenarios to explain the "patterns". + +Even when you throw the JavaScript away and decide to read it to learn some +design patterns, you waste your time. Some designs, mostly the MV*, are +hastily described and just superficially analyzed. + +It really starts a bit off -- again, if it was "Learning Design Patterns with +JavaScript", it would be almost perfect -- and then goes downhill by some lazy +writing and wrong assumptions. diff --git a/content/reviews/books/microservices-in-action.md b/content/reviews/books/microservices-in-action.md index 83b9ae3..1b469d4 100644 --- a/content/reviews/books/microservices-in-action.md +++ b/content/reviews/books/microservices-in-action.md @@ -3,7 +3,7 @@ title = "Microservices In Action - Morgan Bruce" date = 2019-08-13 [taxonomies] -tags = ["books", "en-au", "reviews", "microservices", "morgan bruce"] +tags = ["books", "reviews", "microservices", "morgan bruce", "it"] +++ [GoodReads summary](https://www.goodreads.com/book/show/36579817-microservices-in-action): @@ -35,7 +35,7 @@ they are used for the obvious, it really irks me -- specially 'cause I read those books on a "black background with white letters" and images do not fit that properly, using a white background that usually just hurts my eyes. And by "used for the obvious", there are images follow the description of "A and B -communicate with C" and a large image showing "A --> C <-- B"; was that really +communicate with C" and a large image showing `A --> C <-- B`; was that really necessary? The intro says the code is in Python, and that was something that I'd really diff --git a/content/reviews/books/modern-java-in-action.md b/content/reviews/books/modern-java-in-action.md index f3371be..838f2cb 100644 --- a/content/reviews/books/modern-java-in-action.md +++ b/content/reviews/books/modern-java-in-action.md @@ -3,9 +3,10 @@ title = "Modern Java in Action - Raoul-Gabriel Urma" date = 2019-02-08 [taxonomies] -tags = ["books", "en-au", "reviews", "java", "java 8", "java 9", "raoul-gabriel urma"] +tags = ["books", "reviews", "java", "java 8", "java 9", "raoul-gabriel urma", "it"] +++ +[GoodReads Summary](https://www.goodreads.com/book/show/46213396-modern-java-in-action): Java 8 Lambdas in Action is a clearly-written guide to Java 8 lambdas and functional programming in Java. It begins with a practical introduction to the structure and benefits of lambda expressions in real-world Java code. The book diff --git a/content/reviews/books/modern-vim-craft-your-development-environment-with-vim8-and-neovim.md b/content/reviews/books/modern-vim-craft-your-development-environment-with-vim8-and-neovim.md index cde9bc5..611f64c 100644 --- a/content/reviews/books/modern-vim-craft-your-development-environment-with-vim8-and-neovim.md +++ b/content/reviews/books/modern-vim-craft-your-development-environment-with-vim8-and-neovim.md @@ -3,7 +3,7 @@ title = "Modern Vim: Craft Your Development Environment with Vim 8 and Neovim - date = 2018-12-29 [taxonomies] -tags = ["en-au", "books", "reviews", "vim", "drew neil"] +tags = ["books", "reviews", "vim", "drew neil", "it", "neovim"] +++ [GoodReads Summary](https://www.goodreads.com/book/show/36517607-modern-vim): diff --git a/content/reviews/books/mujica-a-revolucao-tranquila.md b/content/reviews/books/mujica-a-revolucao-tranquila.md index 6a485bd..612c5d3 100644 --- a/content/reviews/books/mujica-a-revolucao-tranquila.md +++ b/content/reviews/books/mujica-a-revolucao-tranquila.md @@ -2,19 +2,43 @@ title = "Mujica – A revolução tranquila - Mauricio Rabuffetti" date = 2017-03-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "mauricio rabuffetti"] +tags = ["books", "pt-br", "mauricio rabuffetti", "uruguai", "mujica", "reviews", "história", "history"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/25792025-mujica-a-revolu-o-tranquila): +A biografia definitiva do líder político mais carismático do mundo. + + + {{ stars(stars=2) }} -Chamar esse livro de "biografia" é um pouco demais. É estranho que um livro que tenha uma pessoa na capa e no título tenha tão pouco espaço para ela. +Chamar esse livro de "biografia" é um pouco demais. É estranho que um livro +que tenha uma pessoa na capa e no título tenha tão pouco espaço para ela. -Parte da história de José Mujica acontece durante a ditatura uruguaia, quando este era guerrilheiro. Embora seja um capítulo importante da vida de Mujica, o autor resolveu não despender tempo o suficiente sobre o assunto porque, segundo o mesmo, há vários outros livros sobre o assunto do qual os uruguaios querem esquecer. Entretanto, mesmo que seja a milésima vez em que algo é falado, ele deve ser contando por questões de posicionar o "tópico" na história. +Parte da história de José Mujica acontece durante a ditatura uruguaia, quando +este era guerrilheiro. Embora seja um capítulo importante da vida de Mujica, o +autor resolveu não despender tempo o suficiente sobre o assunto porque, +segundo o mesmo, há vários outros livros sobre o assunto do qual os uruguaios +querem esquecer. Entretanto, mesmo que seja a milésima vez em que algo é +falado, ele deve ser contando por questões de posicionar o "tópico" na +história. -A mesma coisa acontece com a questão da legalização da maconha. Embora o livro realmente despenda tempo falando sobre a lei do então presidente Mujica, pouco é falado da ação do presidente sobre a liberação e muito mais sobre questões sanitárias da questão: se vicia mais ou menos, como a OEA via a questão da legalização, os relatórios da ONU, etc, etc, etc. A parte que tangencia todas essas questões e Mujica é simplesmente "Mujica levantou a questão da legalização da maconha". +A mesma coisa acontece com a questão da legalização da maconha. Embora o livro +realmente despenda tempo falando sobre a lei do então presidente Mujica, pouco +é falado da ação do presidente sobre a liberação e muito mais sobre questões +sanitárias da questão: se vicia mais ou menos, como a OEA via a questão da +legalização, os relatórios da ONU, etc, etc, etc. A parte que tangencia todas +essas questões e Mujica é simplesmente "Mujica levantou a questão da +legalização da maconha". -Ainda, bem no começo do livro, é dito que o povo uruguaio não vê Mujica como o resto do mundo vê. Esse seria um ponto bem interessante de ser visto -- afinal de contas, aqui nós somos "resto do mundo" -- mas isso nunca é levado a frente. Termina, basicamente, com "algumas pessoas não gostaram do que Mujica fez". Existem alguns pontos, principalmente questões diplomáticas, mas fica basicamente no "não gostaram". +Ainda, bem no começo do livro, é dito que o povo uruguaio não vê Mujica como o +resto do mundo vê. Esse seria um ponto bem interessante de ser visto -- afinal +de contas, aqui nós somos "resto do mundo" -- mas isso nunca é levado a +frente. Termina, basicamente, com "algumas pessoas não gostaram do que Mujica +fez". Existem alguns pontos, principalmente questões diplomáticas, mas fica +basicamente no "não gostaram". -É interessante para se ter uma visão da questão política-diplomática do Uruguai nos tempos de Mujica, mas muito pouco para se ter uma visão diferente do "presidente pobre", como os grandes meios projetaram Mujica. \ No newline at end of file +É interessante para se ter uma visão da questão política-diplomática do +Uruguai nos tempos de Mujica, mas muito pouco para se ter uma visão diferente +do "presidente pobre", como os grandes meios projetaram Mujica. diff --git a/content/reviews/books/mussum-forevis-samba-me-e-trapalhoes.md b/content/reviews/books/mussum-forevis-samba-me-e-trapalhoes.md index c6fa155..cd70dce 100644 --- a/content/reviews/books/mussum-forevis-samba-me-e-trapalhoes.md +++ b/content/reviews/books/mussum-forevis-samba-me-e-trapalhoes.md @@ -2,17 +2,43 @@ title = "Mussum Forévis: Samba, mé e trapalhões - Juliano Barreto" date = 2016-02-21 -category = "review" - [taxonomies] -tags = ["books", "en-au", "juliano barreto"] +tags = ["books", "juliano barreto", "pt-br", "reviews", "história", "history"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/23751843-mussum-for-vis): +Antonio Carlos Bernardes Gomes, mais conhecido como Mussum, é um dos mais +amados humoristas brasileiros. Mas você sabia que ele também era sambista? E +que era torcedor fanático da Mangueira? E que serviu a Aeronáutica? Mussum é +cultuado inclusive por quem não teve a oportunidade de vê-lo junto a Didi, +Dedé e Zacarias no saudoso programa Os Trapalhões. Mussum forévis, a primeira +biografia deste ídolo e artista multifacetado traz detalhes não só sobre sua +carreira na TV, mas como músico em conjuntos como Os 7 Modernos e Os originais +do samba. Este último inclusive costumava se apresentar como banda de apoio de +artistas do porte de Elis Regina, Jorge Ben, Jair Rodrigues, Martinho da Vila +e Baden Powell. + + + {{ stars(stars=4) }} -Esse foi um livro que eu comprei, inicialmente, simplesmente porque estava em promoção. No entanto, há tanta informação histórica no conteúdo que eu posso afirmar, categoricamente, que foi uma das minhas melhores compras. +Esse foi um livro que eu comprei, inicialmente, simplesmente porque estava em +promoção. No entanto, há tanta informação histórica no conteúdo que eu posso +afirmar, categoricamente, que foi uma das minhas melhores compras. -Seguindo a história de Antônio Carlos Bernardes Gomes, o conhecido Mussum, o livro explora desde a infância nas ruas do futuro humorista, passando por seu período de cadete militar (na aeronáutica), cobrindo a parte de sambista integrante de Os Originais do Samba e concluindo com a morte do humorista, parte integrante de Os Trapalhões. +Seguindo a história de Antônio Carlos Bernardes Gomes, o conhecido Mussum, o +livro explora desde a infância nas ruas do futuro humorista, passando por seu +período de cadete militar (na aeronáutica), cobrindo a parte de sambista +integrante de Os Originais do Samba e concluindo com a morte do humorista, +parte integrante de Os Trapalhões. -Não apenas focando na pessoa-título, o livro também mostra a cena cultural e política desde os anos 50, quando Mussum passou a fazer parte dos Originais do Samba até o período em que era figurinha certa nos filmes dos Trapalhões. Obviamente, isso faz com que o livro se torne maior do que o necessário -- alguns pontos são interessantes, mas não necessariamente ligados à vida de Antônio Carlos -- mas nem por isso o conteúdo deixa de ser informativo. +Não apenas focando na pessoa-título, o livro também mostra a cena cultural e +política desde os anos 50, quando Mussum passou a fazer parte dos Originais do +Samba até o período em que era figurinha certa nos filmes dos Trapalhões. +Obviamente, isso faz com que o livro se torne maior do que o necessário -- +alguns pontos são interessantes, mas não necessariamente ligados à vida de +Antônio Carlos -- mas nem por isso o conteúdo deixa de ser informativo. -PS: Acabei esquecendo de mencionar: A forma como o livro foi escrito é de uma acessibilidade tão grande que eu consegui ler todas as 440 páginas em apenas 3 dias. \ No newline at end of file +PS: Acabei esquecendo de mencionar: A forma como o livro foi escrito é de uma +acessibilidade tão grande que eu consegui ler todas as 440 páginas em apenas 3 +dias. diff --git a/content/reviews/books/nginx-from-beginner-to-pro.md b/content/reviews/books/nginx-from-beginner-to-pro.md index f0aaae1..29235d9 100644 --- a/content/reviews/books/nginx-from-beginner-to-pro.md +++ b/content/reviews/books/nginx-from-beginner-to-pro.md @@ -2,15 +2,33 @@ title = "Nginx: From Beginner to Pro - Rahul Soni" date = 2017-06-28 -category = "review" - [taxonomies] -tags = ["books", "en-au", "rahul soni"] +tags = ["books", "rahul soni", "reviews", "nginx", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/30892392-nginx): +Teaches you to start up Nginx and quickly take your expertise to a level where +you can comfortably work with various aspects of the web server and make +informed design decisions for your web farm. Nginx powers more than 40% of the +top 1000 websites and is among the handful of web servers that can handle more +than 10K simultaneous connections. It has some features which are simply +unparalleled. + + + {{ stars(stars=1) }} -Seriously, I had to read this with a lot of self control, because there was so much bullshit. I mean, you don't need to know Nginx to understand that the PID file is used to know if the process is running (in the most simple case) but the book tries to sell it as a way to check process uptime. I mean, seriously? Of all the things, Nginx will create a PID file simply for you to check its uptime? +Seriously, I had to read this with a lot of self control, because there was so +much bullshit. I mean, you don't need to know Nginx to understand that the PID +file is used to know if the process is running (in the most simple case) but +the book tries to sell it as a way to check process uptime. I mean, seriously? +Of all the things, Nginx will create a PID file simply for you to check its +uptime? -This kind of thing keeps going on and on. It feels like the author didn't know Nginx at all and was figuring out as the book was being written; when they had no idea what one thing meant, bullshit was used to fill the blanks. +This kind of thing keeps going on and on. It feels like the author didn't know +Nginx at all and was figuring out as the book was being written; when they had +no idea what one thing meant, bullshit was used to fill the blanks. -This means two things: One, there is so much bullshit it is painful. Second, the book only gets reasonably good at the end. But still hardly anything near the "Pro" as used in the title. \ No newline at end of file +This means two things: One, there is so much bullshit it is painful. Second, +the book only gets reasonably good at the end. But still hardly anything near +the "Pro" as used in the title. diff --git a/content/reviews/books/night-of-the-living-trekkies.md b/content/reviews/books/night-of-the-living-trekkies.md index 045e6be..5df9195 100644 --- a/content/reviews/books/night-of-the-living-trekkies.md +++ b/content/reviews/books/night-of-the-living-trekkies.md @@ -2,17 +2,30 @@ title = "Night of the Living Trekkies - Kevin David Anderson" date = 2018-08-28 -category = "review" - [taxonomies] -tags = ["books", "en-au", "kevin david anderson"] +tags = ["books", "kevin david anderson", "reviews", "star trek", "zombies", "fiction"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/7884969-night-of-the-living-trekkies): +Jim Pike, the disillusioned manager of a hotel that is hosting a Star Trek +convention, finds himself leading a ragtag crew of survivors as a strange +virus turns the convention-goers into zombies... + + + {{ stars(stars=5) }} -I'm not a fan of zombie movies/books. But I'm a Star Trek fan. And oh boy, this is a fun book. +I'm not a fan of zombie movies/books. But I'm a Star Trek fan. And oh boy, +this is a fun book. -While some events in the story may be too cliché (specially in the zombie genre), the way the author interweaves with Star Trek philosophy and Trek fandom is brilliant. And also gets bonus points for not doing "A red shirt on the Enterprise gets infected with a virus and starts zombifying everyone"; instead, it takes the *fandom* and infects its. +While some events in the story may be too cliché (specially in the zombie +genre), the way the author interweaves with Star Trek philosophy and Trek +fandom is brilliant. And also gets bonus points for not doing "A red shirt on +the Enterprise gets infected with a virus and starts zombifying everyone"; +instead, it takes the *fandom* and infects its. -And while the cliché parts, although cliché, fit the story, the fact that the author also goes into deep in what Star Trek is and what it represents to its fans, it's pretty damn amazing. +And while the cliché parts, although cliché, fit the story, the fact that the +author also goes into deep in what Star Trek is and what it represents to its +fans, it's pretty damn amazing. -I really really liked it. \ No newline at end of file +I really really liked it. diff --git a/content/reviews/books/nos-bastidores-da-coca-cola.md b/content/reviews/books/nos-bastidores-da-coca-cola.md index 4a26bc0..fbe7ecb 100644 --- a/content/reviews/books/nos-bastidores-da-coca-cola.md +++ b/content/reviews/books/nos-bastidores-da-coca-cola.md @@ -2,19 +2,43 @@ title = "Nos Bastidores da Coca-Cola - Neville Isdell" date = 2017-01-14 -category = "review" - [taxonomies] -tags = ["books", "en-au", "neville isdell"] +tags = ["books", "pt-br", "neville isdell", "história", "coca-cola", "ceo"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/26831728-nos-bastidores-da-coca-cola): +A Coca-Cola é a marca mais reconhecida e próspera do mundo, cruzando +fronteiras geográficas, linguísticas e culturais. A história da criação, do +marketing e da recriação da marca é contada pela primeira vez por um executivo +da própria companhia. Um homem cuja carreira de mais de quarenta anos o levou +a viajar o mundo inteiro e a escalar da base até o topo da pirâmide. + + + {{ stars(stars=2) }} -O grande problema com biografias -- ou apresentações de história na primeira pessoa -- é que é esperado que a pessoa conte sobre o que o autor sentiu; caso contrário, tudo se torna tão impessoal que o mesmo parece uma ficção. +O grande problema com biografias -- ou apresentações de história na primeira +pessoa -- é que é esperado que a pessoa conte sobre o que o autor sentiu; caso +contrário, tudo se torna tão impessoal que o mesmo parece uma ficção. -Em _Always Looking Up: The Adventures of an Incurable Optimist_, Neil Peart soa impessoal e começa a cair nessa categoria de "parece ficção", mas junto com o livro estão as cartas enviadas a um amigo, o que o trás de volta para o lado humano. Em "Nos Bastidores da Coca-Cola", Neville Isdell nunca fala de como se sente, e deixa uma sensação tão grande de "desumanidade" que até quando fala da esposa, parece que o único mérito da mesma é que ela o apoiou. +Em _Always Looking Up: The Adventures of an Incurable Optimist_, Neil Peart +soa impessoal e começa a cair nessa categoria de "parece ficção", mas junto +com o livro estão as cartas enviadas a um amigo, o que o trás de volta para o +lado humano. Em "Nos Bastidores da Coca-Cola", Neville Isdell nunca fala de +como se sente, e deixa uma sensação tão grande de "desumanidade" que até +quando fala da esposa, parece que o único mérito da mesma é que ela o apoiou. -Existem alguns casos interessantes de história mesmo, mas a narrativa se torna cansativa pois a visão do autor é sempre de que o mesmo resolveu o problema e, mais pra frente, houveram mais pessoas envolvidas. Foi sempre *ele* quem resolveu o problema, não o grupo. Sempre no singular. +Existem alguns casos interessantes de história mesmo, mas a narrativa se torna +cansativa pois a visão do autor é sempre de que o mesmo resolveu o problema e, +mais pra frente, houveram mais pessoas envolvidas. Foi sempre *ele* quem +resolveu o problema, não o grupo. Sempre no singular. -E o último capítulo não fala nada de Coca-Cola. Trata-se de sua visão de economia, da qual a Coca-Cola sequer faz parte. +E o último capítulo não fala nada de Coca-Cola. Trata-se de sua visão de +economia, da qual a Coca-Cola sequer faz parte. -Com relação à tradução: Embora a tradução tenha se preocupado em fazer um livro bom de ler, peca-se horrendamente quando se fala da Coca-Cola. Algumas vezes é "Coca-Cola", outras é "Coke". Poderia ser que uma refere-se à bebida e a outra à empresa (ou vice-versa), mas não. É como se o tradutor -- ou mesmo o autor, nesse ponto -- não consiga ter uma visão do que é uma e o que é a outra. \ No newline at end of file +Com relação à tradução: Embora a tradução tenha se preocupado em fazer um +livro bom de ler, peca-se horrendamente quando se fala da Coca-Cola. Algumas +vezes é "Coca-Cola", outras é "Coke". Poderia ser que uma refere-se à bebida e +a outra à empresa (ou vice-versa), mas não. É como se o tradutor -- ou mesmo o +autor, nesse ponto -- não consiga ter uma visão do que é uma e o que é a +outra. diff --git a/content/reviews/books/o-heroi-de-mil-faces.md b/content/reviews/books/o-heroi-de-mil-faces.md index fb6a7d3..3aab5b9 100644 --- a/content/reviews/books/o-heroi-de-mil-faces.md +++ b/content/reviews/books/o-heroi-de-mil-faces.md @@ -2,23 +2,58 @@ title = "O Herói de Mil Faces - Joseph Campbell" date = 2016-01-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "joseph campbell"] +tags = ["books", "pt-br", "joseph campbell", "reviews", "filosofia"] +++ -{{ stars(stars=1) }} - -Vou admitir que o livro ganhou de mim. Desisti de continuar lendo depois de chegar na metade. -Não que o conceito de um monomito não fosse interessante o suficiente para ler o livro até o final. Campbell ainda faz a questão ser mais interessante ligando os pontos e conceitos do monomito com questões sociais e psicológicas reais. +[Resumo GoodReads](https://www.goodreads.com/book/show/6406621-o-her-i-de-mil-faces): +Apolo, Thor, Buda e outros numerosos protagonistas das religiões, mitologias, +contos de fada e do folclore universal representam simultaneamente as várias +fases de uma mesma história. O relacionamento entre seus símbolos intemporais +e os detectados nos sonhos pela moderna psicologia profunda é o ponto de +partida da interpretação oferecida por Joseph Campbell reconhecidamente, um +dos maiores estudiosos e mais profundos intérpretes da mitologia universal, +neste clássico obrigatório para compreender esse monomito que é a jornada do +herói. -Acontece que Campbell, para provar seu ponto, basea-se em mitos não comuns ao ocidente. Se o monomito fosse 100% correto, não importaria a origem do mito, haveriam interligações com mitos conhecidos daqui; entretanto, 95% dos mitos citados são orientais, não difundidos: mitos japoneses (nada como Musashi), muçulmanos, africanos, aborígenes (da Austrália)... O que levanta a questão de quão difundido é o mito ou, caso você esteja usando o "chapéu de ceticismo", se o mito realmente existe ou se Campbell criou apenas para provar um ponto. + -Mitos como os gregos conhecidos -- Hércules e seus 12 trabalhos, por exemplo -- não são falados; Buda aparece, mas em coisas que apenas um budista conheceria; Jesus aprece de relance... Tudo isso torna difícil acreditar que os pontos são reais. - -Os pontos em si são complexos de serem explicados, justamente por causa da base psicológica e sociológica presente. Nesse ponto é onde surge um mito não popular que deve ser contado. E assim você está lendo 4 páginas já sobre um mito e esqueceu completamente o ponto que o autor queria chegar. Ou então é apenas uma continuação de um mito começado dois capítulos atrás, que você já esqueceu os pormenores que fazem com que o ponto faça sentido. - -Ainda: O texto original é de 1949, um tempo em que escrever bem significava escrever muito. Existem parágrafos gigantescos de uma frase só e páginas inteiras que são apenas um parágrafo. A tradução de 1989 não ajuda nem um pouco e a combinação dos dois simplesmente te faz perguntar o que diabos o autor e o tradutor fumaram durante seus trabalhos. +{{ stars(stars=1) }} -O monomito parece ser realmente correto, mas para isso existem filmes de 3 minutos que conseguem explicar todos os pontos de forma sucinta e com mitos comuns hoje. Veja os filmes e esqueça o livro. \ No newline at end of file +Vou admitir que o livro ganhou de mim. Desisti de continuar lendo depois de +chegar na metade. + +Não que o conceito de um monomito não fosse interessante o suficiente para ler +o livro até o final. Campbell ainda faz a questão ser mais interessante +ligando os pontos e conceitos do monomito com questões sociais e psicológicas +reais. + +Acontece que Campbell, para provar seu ponto, basea-se em mitos não comuns ao +ocidente. Se o monomito fosse 100% correto, não importaria a origem do mito, +haveriam interligações com mitos conhecidos daqui; entretanto, 95% dos mitos +citados são orientais, não difundidos: mitos japoneses (nada como Musashi), +muçulmanos, africanos, aborígenes (da Austrália)... O que levanta a questão de +quão difundido é o mito ou, caso você esteja usando o "chapéu de ceticismo", +se o mito realmente existe ou se Campbell criou apenas para provar um ponto. + +Mitos como os gregos conhecidos -- Hércules e seus 12 trabalhos, por exemplo +-- não são falados; Buda aparece, mas em coisas que apenas um budista +conheceria; Jesus aprece de relance... Tudo isso torna difícil acreditar que +os pontos são reais. + +Os pontos em si são complexos de serem explicados, justamente por causa da +base psicológica e sociológica presente. Nesse ponto é onde surge um mito não +popular que deve ser contado. E assim você está lendo 4 páginas já sobre um +mito e esqueceu completamente o ponto que o autor queria chegar. Ou então é +apenas uma continuação de um mito começado dois capítulos atrás, que você já +esqueceu os pormenores que fazem com que o ponto faça sentido. + +Ainda: O texto original é de 1949, um tempo em que escrever bem significava +escrever muito. Existem parágrafos gigantescos de uma frase só e páginas +inteiras que são apenas um parágrafo. A tradução de 1989 não ajuda nem um +pouco e a combinação dos dois simplesmente te faz perguntar o que diabos o +autor e o tradutor fumaram durante seus trabalhos. + +O monomito parece ser realmente correto, mas para isso existem filmes de 3 +minutos que conseguem explicar todos os pontos de forma sucinta e com mitos +comuns hoje. Veja os filmes e esqueça o livro. diff --git a/content/reviews/books/o-principe.md b/content/reviews/books/o-principe.md index 446af3a..3a31af3 100644 --- a/content/reviews/books/o-principe.md +++ b/content/reviews/books/o-principe.md @@ -2,15 +2,34 @@ title = "O Príncipe - Niccolò Machiavelli" date = 2016-11-28 -category = "review" - [taxonomies] -tags = ["books", "en-au", "niccolo machiavelli"] +tags = ["books", "pt-br", "niccolo machiavelli", "reviews", "ficção"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/28551872-o-pr-ncipe): +O Príncipe é um livro que não sai de moda. Mais do que um best-seller, ele é +um clássico. Surgem novas edições e grandes estadistas encontram nesta obra +suas virtudes literárias e estratégicas. Silvio Berlusconi, presidente do +Conselho de Ministros da República italiana, apresentava assim esta obra, ao +dá-la como presente de Natal para amigos e colaboradores em 1992: "O Príncipe +é o primeiro clássico do pensamento político moderno, referência durante +gerações para estadistas e diplomatas. A obra foi concebida como um conjunto +de reflexões do autor sobre a arte de conquistar e conservar o poder em um +principado." + + {{ stars(stars=3) }} -Esse é o livro que gerou a expressão "maquiavélico" (e seus derivados). Eu acredito que a parte inicial do mesmo, em que Maquiavel aponta que o livro é um presente para um novo príncipe, foi cortada dessa edição, mas posso estar enganado. +Esse é o livro que gerou a expressão "maquiavélico" (e seus derivados). Eu +acredito que a parte inicial do mesmo, em que Maquiavel aponta que o livro é +um presente para um novo príncipe, foi cortada dessa edição, mas posso estar +enganado. -Um dos problemas dessa tradução -- mas que é explicado logo na introdução do livro -- é que, por ser baseado num texto em italiano antigo, o mesmo foi traduzido para um português mais rebuscado (praticamente um barroco). Algumas partes são excruciantes de ler. +Um dos problemas dessa tradução -- mas que é explicado logo na introdução do +livro -- é que, por ser baseado num texto em italiano antigo, o mesmo foi +traduzido para um português mais rebuscado (praticamente um barroco). Algumas +partes são excruciantes de ler. -Fora isso, O Príncipe fala muito de como manter o poder a qualquer custo. E é impossível não ler e não pensar em vários políticos nacionais brasileiros, que aparentemente seguem o livrinho a risca. \ No newline at end of file +Fora isso, O Príncipe fala muito de como manter o poder a qualquer custo. E é +impossível não ler e não pensar em vários políticos nacionais brasileiros, que +aparentemente seguem o livrinho a risca. diff --git a/content/reviews/books/object-oriented-javascript-second-edition.md b/content/reviews/books/object-oriented-javascript-second-edition.md index 1dc2840..6a8261b 100644 --- a/content/reviews/books/object-oriented-javascript-second-edition.md +++ b/content/reviews/books/object-oriented-javascript-second-edition.md @@ -2,17 +2,36 @@ title = "Object-oriented JavaScript - Second Edition - Stoyan Stefanov" date = 2015-10-03 -category = "review" - [taxonomies] -tags = ["books", "en-au", "stoyan stefanov"] +tags = ["books", "stoyan stefanov", "javascript", "it", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/4355468-object-oriented-javascript): +Create scalable and reusable high-quality JavaScript applications and +libraries using the concepts of object-oriented programming. This book is for +the beginning to intermediate web developer who wants to solve web development +problems with smart JavaScript. It does not assume any prior knowledge of +JavaScript programming; however even if you already know some JavaScript, +there will be plenty for you to learn here. + + + {{ stars(stars=3) }} -Javascript is a weird language. Good practices make a weird language easier to understand and read. That's why I was interested in writing OO JS code. +Javascript is a weird language. Good practices make a weird language easier to +understand and read. That's why I was interested in writing OO JS code. -Thing is, this book is not just about OO. There is a bunch of "hey, if you never heard about JS, here is how it works", which I believe is kinda pointless (there are plenty "Starting with JS" books these days), there is a bunch of browser objects (which, although "objects", I don't believe they are necessary to write OO JS code) and there is plenty about reserved words and what they mean (which although nice, is also unnecessary). +Thing is, this book is not just about OO. There is a bunch of "hey, if you +never heard about JS, here is how it works", which I believe is kinda +pointless (there are plenty "Starting with JS" books these days), there is a +bunch of browser objects (which, although "objects", I don't believe they are +necessary to write OO JS code) and there is plenty about reserved words and +what they mean (which although nice, is also unnecessary). -There is also a bunch of mentions of things some "Douglas Crockford" which made me wonder why I was reading this book instead of looking for stuff Crockford wrote. +There is also a bunch of mentions of things some "Douglas Crockford" which +made me wonder why I was reading this book instead of looking for stuff +Crockford wrote. -But the book explores all possibilities of writing OO code in a non-OO language, have some design patterns in JS and some JS patterns which are interesting. \ No newline at end of file +But the book explores all possibilities of writing OO code in a non-OO +language, have some design patterns in JS and some JS patterns which are +interesting. diff --git a/content/reviews/books/oh-myyy-there-goes-the-internet-life-the-internet-and-everything.md b/content/reviews/books/oh-myyy-there-goes-the-internet-life-the-internet-and-everything.md index 23b07a0..7493999 100644 --- a/content/reviews/books/oh-myyy-there-goes-the-internet-life-the-internet-and-everything.md +++ b/content/reviews/books/oh-myyy-there-goes-the-internet-life-the-internet-and-everything.md @@ -2,13 +2,24 @@ title = "Oh Myyy! (There Goes the Internet): Life, the Internet and Everything - George Takei" date = 2015-09-18 -category = "review" - [taxonomies] -tags = ["books", "en-au", "george takei"] +tags = ["books", "george takei", "reviews", "star trek"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/16059137-oh-myyy): +How did a 75-year old actor from Star Trek become a social media juggernaut? +Why does everything he posts spread like wildfire across the ether, with tens +or even hundreds of thousands of likes and shares? And what can other sites, +celebrities and companies do to attain his stratospheric engagement levels, +which hover or top 100 percent while theirs languish in the single digits? + + + {{ stars(stars=2) }} -Ok, totally my fault, but I bought the book expecting a bit about Takei history, but all I got was "how to be successful on Facebook". +Ok, totally my fault, but I bought the book expecting a bit about Takei +history, but all I got was "how to be successful on Facebook". -Don't get me wrong, it's not a bad book. It's easy to read and have its fun moments, but there is nothing about Takei himself -- again, my fault, I was expecting a biography when I didn't read the summary. \ No newline at end of file +Don't get me wrong, it's not a bad book. It's easy to read and have its fun +moments, but there is nothing about Takei himself -- again, my fault, I was +expecting a biography when I didn't read the summary. diff --git a/content/reviews/books/old-mans-war-old-mans-war-1.md b/content/reviews/books/old-mans-war-old-mans-war-1.md index 62d437c..bb7b9d3 100644 --- a/content/reviews/books/old-mans-war-old-mans-war-1.md +++ b/content/reviews/books/old-mans-war-old-mans-war-1.md @@ -2,19 +2,39 @@ title = "Old Man's War (Old Man's War, #1) - John Scalzi" date = 2015-07-19 -category = "review" - [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "reviews", "scifi", "old man's war"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/36510196-old-man-s-war): +Earth itself is a backwater. The bulk of humanity's resources are in the hands +of the Colonial Defense Force. Everybody knows that when you reach retirement +age, you can join the CDF. They don't want young people; they want people who +carry the knowledge and skills of decades of living. You'll be taken off Earth +and never allowed to return. You'll serve two years at the front. And if you +survive, you'll be given a generous homestead stake of your own, on one of our +hard-won colony planets. + + + {{ stars(stars=4) }} -"Old Man's War" was a long time in my "to read" list. Today I finally finished reading it. +"Old Man's War" was a long time in my "to read" list. Today I finally finished +reading it. -I've been following Scalzi for some time on Twitter and he always post intelligent comments. I read _Subterranean Scalzi Super Bundle_ and really enjoyed his writing style. The very first book of his was, then, an obvious choice. +I've been following Scalzi for some time on Twitter and he always post +intelligent comments. I read _Subterranean Scalzi Super Bundle_ and really +enjoyed his writing style. The very first book of his was, then, an obvious +choice. -"Old Man's War" is part _The Forever War_. It's war on space. You have spaceships and soldiers with special training and special weapons. +"Old Man's War" is part _The Forever War_. It's war on space. You have +spaceships and soldiers with special training and special weapons. -But while you read about the military life like in "Starship Troopers", it also has no qualms in killing interesting characters to show that not all things in war are easy and the bad guys always lose, like in "All Quiet". +But while you read about the military life like in "Starship Troopers", it +also has no qualms in killing interesting characters to show that not all +things in war are easy and the bad guys always lose, like in "All Quiet". -The story starts really strong, gets more cerebral in the middle and then slows a bit in the end. Still pretty enjoyable, specially if you liked the books I mentioned before. The fact that they way Scalzi writes makes it easy to read is also a plus. \ No newline at end of file +The story starts really strong, gets more cerebral in the middle and then +slows a bit in the end. Still pretty enjoyable, specially if you liked the +books I mentioned before. The fact that they way Scalzi writes makes it easy +to read is also a plus. diff --git a/content/reviews/books/one-day-on-mars.md b/content/reviews/books/one-day-on-mars.md index ae54841..19b77d1 100644 --- a/content/reviews/books/one-day-on-mars.md +++ b/content/reviews/books/one-day-on-mars.md @@ -3,7 +3,7 @@ title = "One Day On Mars - Travis S. Taylor" date = 2019-12-13 [taxonomies] -tags = ["en-au", "books", "reviews", "travis s taylor", "sci-fi", "mars"] +tags = ["books", "reviews", "travis s taylor", "scifi", "mars"] +++ [GoodReads Summary](https://www.goodreads.com/book/show/20638066-one-day-on-mars): diff --git a/content/reviews/books/pense-como-um-freak.md b/content/reviews/books/pense-como-um-freak.md index 484bcd1..9542a50 100644 --- a/content/reviews/books/pense-como-um-freak.md +++ b/content/reviews/books/pense-como-um-freak.md @@ -2,17 +2,35 @@ title = "Pense Como Um Freak - Steven D. Levitt" date = 2016-02-28 -category = "review" - [taxonomies] -tags = ["books", "en-au", "steven d. levitt"] +tags = ["books", "pt-br", "steven d. levitt", "reviews", "psicologia"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/24689125-pense-como-um-freak): +The New York Times bestselling Freakonomics changed the way we see the world, +exposing the hidden side of just about everything. Then came +SuperFreakonomics, a documentary film, an award-winning podcast, and more. + +Now, with Think Like a Freak, Steven D. Levitt and Stephen J. Dubner have +written their most revolutionary book yet. With their trademark blend of +captivating storytelling and unconventional analysis, they take us inside +their thought process and teach us all to think a bit more productively, more +creatively, more rationally—to think, that is, like a Freak. + + + {{ stars(stars=5) }} -"Pense como um freak" é mais um dos livros da série do Freakonomics, onde coisas aparentemente sem conexão são mostradas como possíveis correlações. +"Pense como um freak" é mais um dos livros da série do Freakonomics, onde +coisas aparentemente sem conexão são mostradas como possíveis correlações. -Nesse livro, Levitt e Dubner explicam algumas das "técnicas" que usam tanto para detectar coisas sem conexões óbvias como para explicar os resultados depois. +Nesse livro, Levitt e Dubner explicam algumas das "técnicas" que usam tanto +para detectar coisas sem conexões óbvias como para explicar os resultados +depois. -E, obviamente, não poderiam faltar as conclusões mostrando que coisas aparentemente sem conexão na verdade estão relacionadas. +E, obviamente, não poderiam faltar as conclusões mostrando que coisas +aparentemente sem conexão na verdade estão relacionadas. -A parte interessante é que o livro termina nos 70%. Os demais 30% são divididos entre um índice gigantesco de assuntos abordados e a lista de referências utilizadas para chegarem as conclusões apresentadas. \ No newline at end of file +A parte interessante é que o livro termina nos 70%. Os demais 30% são +divididos entre um índice gigantesco de assuntos abordados e a lista de +referências utilizadas para chegarem as conclusões apresentadas. diff --git a/content/reviews/books/poder-manipulacao-como-entender-o-mundo-em-vinte-licoes-extraidas-de-o-principe-de-maquiavel.md b/content/reviews/books/poder-manipulacao-como-entender-o-mundo-em-vinte-licoes-extraidas-de-o-principe-de-maquiavel.md index 2d9ab21..dccb5f9 100644 --- a/content/reviews/books/poder-manipulacao-como-entender-o-mundo-em-vinte-licoes-extraidas-de-o-principe-de-maquiavel.md +++ b/content/reviews/books/poder-manipulacao-como-entender-o-mundo-em-vinte-licoes-extraidas-de-o-principe-de-maquiavel.md @@ -2,15 +2,38 @@ title = "Poder & Manipulação: Como entender o mundo em vinte lições extraídas de \"O Príncipe\", de Maquiavel - Jacob Pétry" date = 2016-08-27 -category = "review" - [taxonomies] -tags = ["books", "en-au", "jacob petry"] +tags = ["books", "pt-br", "jacob petry", "o príncipe", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/30321814-poder-manipula-o): +Nesta edição, fruto de um trabalho único na história, os ensinamentos de +Maquiavel se tornam mais relacionados ao mundo atual. "Poder & Manipulação" +não é simplesmente uma nova tradução, mas uma edição da obra original, tal +como seria se ela estivesse sendo publicada agora, pela primeira vez, focada +nos temas perenes, relevantes ao mundo de hoje. E vai além: inclui uma análise +objetiva das vinte estratégias mais importantes do clássico. Ao compreender +estas lições, o leitor estará mais bem preparado para defender-se das pessoas +manipuladoras e de posse de ferramentas para agir com mais segurança, ousadia +e astúcia diante da vida. + + + {{ stars(stars=2) }} -"O Príncipe" é, basicamente, um livro para perder a fé na humanidade. Tudo se relaciona com o poder e como mantê-lo; como convencer os outros de que você é a resposta certa e os demais estão raros -- uma fato que, se olhar as figuras que tem aparecido no final de 2016, torna-se contuendemente óbvias, utilizando os princípios "maquiavélicos" para se propagar na atmosfera política. +"O Príncipe" é, basicamente, um livro para perder a fé na humanidade. Tudo se +relaciona com o poder e como mantê-lo; como convencer os outros de que você é +a resposta certa e os demais estão raros -- uma fato que, se olhar as figuras +que tem aparecido no final de 2016, torna-se contuendemente óbvias, utilizando +os princípios "maquiavélicos" para se propagar na atmosfera política. -Entretanto, esse livro não é O Príncipe. Esse livro é uma análise sobre O Príncipe. E embora a escolha de trechos tenha sido muito interessante, a análise fica devendo muito para com o conteúdo. Enquanto o príncipe fala, por exemplo, como a Alemanha se manteve unida, pronta pra guerra e adorando seu líder, a análise resolve falar de... pessoas tímidas? O que é que A tem a ver com B? +Entretanto, esse livro não é O Príncipe. Esse livro é uma análise sobre O +Príncipe. E embora a escolha de trechos tenha sido muito interessante, a +análise fica devendo muito para com o conteúdo. Enquanto o príncipe fala, por +exemplo, como a Alemanha se manteve unida, pronta pra guerra e adorando seu +líder, a análise resolve falar de... pessoas tímidas? O que é que A tem a ver +com B? -De novo, O Príncipe parece ser, pelos trechos escolhidos, bem interessante. A análise, conteúdo desse livro, no entanto, parece se referenciar a algo completamente diferente. \ No newline at end of file +De novo, O Príncipe parece ser, pelos trechos escolhidos, bem interessante. A +análise, conteúdo desse livro, no entanto, parece se referenciar a algo +completamente diferente. diff --git a/content/reviews/books/powers-annals-of-the-western-shore-3.md b/content/reviews/books/powers-annals-of-the-western-shore-3.md index 94927c9..18272c8 100644 --- a/content/reviews/books/powers-annals-of-the-western-shore-3.md +++ b/content/reviews/books/powers-annals-of-the-western-shore-3.md @@ -2,23 +2,48 @@ title = "Powers (Annals of the Western Shore, #3) - Ursula K. Le Guin" date = 2018-05-27 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ursula k. le guin"] +tags = ["books", "ursula k. le guin", "reviews", "annals of the western shore", "fantasy"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/68020.Powers): +Young Gav can remember the page of a book after seeing it once, and, +inexplicably, he sometimes "remembers" things that are going to happen in the +future. As a loyal slave, he must keep these powers secret, but when a +terrible tragedy occurs, Gav, blinded by grief, flees the only world he has +ever known. + + + {{ stars(stars=5) }} "The story of a boy becoming a man." + Or "The story of a slave becoming a freeman." + Or "The story of a man traveling across its country." -All those could serve as a quick description of the story. And all of them would be, at least, a bit wrong. +All those could serve as a quick description of the story. And all of them +would be, at least, a bit wrong. Because it's not just one of those. It's all of those. And a bit more. -At first, I was quite disappointed 'cause the "Powers" at the title are mentioned very early and then... nothing. There is a lot of going back and forth (a few transitions are a bit weird, like suddenly the story being a letter to the protagonist's wife) and you keep thinking "Were the heck is this going on?" And then, suddenly, you keep reading a bit more because you want to see a thread closed, and then read more, and more, and more... It's quite the same feeling I got from _Changing Planes_, although the story here is way more complex (not quite hard, as Changing Planes is a bunch of separate stories instead of the continuous story of a slave who runs away, make friends, finds his people, in a span of 10 or so years). - -One of the things that Le Guin impresses me is how the way she describes things approaches the way _Isaac Asimov_ does: Describes the very minimum necessary for the reader to understand why the characters are doing something, and let their imagination soar with the rest. It's quite different from _Arthur C Clarke_, which likes to over describe stuff. - -In the end, it was a story that I was mostly uninterested at first but that deeply moved me in the very end. \ No newline at end of file +At first, I was quite disappointed 'cause the "Powers" at the title are +mentioned very early and then... nothing. There is a lot of going back and +forth (a few transitions are a bit weird, like suddenly the story being a +letter to the protagonist's wife) and you keep thinking "Were the heck is this +going on?" And then, suddenly, you keep reading a bit more because you want to +see a thread closed, and then read more, and more, and more... It's quite the +same feeling I got from _Changing Planes_, although the story here is way more +complex (not quite hard, as Changing Planes is a bunch of separate stories +instead of the continuous story of a slave who runs away, make friends, finds +his people, in a span of 10 or so years). + +One of the things that Le Guin impresses me is how the way she describes +things approaches the way _Isaac Asimov_ does: Describes the very minimum +necessary for the reader to understand why the characters are doing something, +and let their imagination soar with the rest. It's quite different from +_Arthur C Clarke_, which likes to over describe stuff. + +In the end, it was a story that I was mostly uninterested at first but that +deeply moved me in the very end. diff --git a/content/reviews/books/princesses-behaving-badly-real-stories-from-history-without-the-fairy-tale-endings.md b/content/reviews/books/princesses-behaving-badly-real-stories-from-history-without-the-fairy-tale-endings.md index 6ec0d1e..eaee0d3 100644 --- a/content/reviews/books/princesses-behaving-badly-real-stories-from-history-without-the-fairy-tale-endings.md +++ b/content/reviews/books/princesses-behaving-badly-real-stories-from-history-without-the-fairy-tale-endings.md @@ -2,17 +2,25 @@ title = "Princesses Behaving Badly: Real Stories from History Without the Fairy-Tale Endings - Linda Rodríguez McRobbie" date = 2018-06-16 -category = "review" - [taxonomies] -tags = ["books", "en-au", "linda rodriguez mcrobbie"] +tags = ["books", "linda rodriguez mcrobbie", "reviews", "history"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/36297174-princesses-behaving-badly): +(No summary.) + + + {{ stars(stars=4) }} One book that came with a Humble Bundle. -Although the title may sound a bit of feminist, the book has nothing about it. Surely, it breaks the mold of “princesses are nice and quiet and beautiful and a man saves them in the end”, but some of the examples are not role models. +Although the title may sound a bit of feminist, the book has nothing about it. +Surely, it breaks the mold of “princesses are nice and quiet and beautiful and +a man saves them in the end”, but some of the examples are not role models. -Princesses that were crazy. Princesses that were princesses just because they lied about it. Princesses that acted more like men. Sadly, there are were few Princess (later queen) Victoria, a princess that proved her worth. +Princesses that were crazy. Princesses that were princesses just because they +lied about it. Princesses that acted more like men. Sadly, there are were few +Princess (later queen) Victoria, a princess that proved her worth. -Still, is a curious history book. \ No newline at end of file +Still, is a curious history book. diff --git a/content/reviews/books/pro-vim.md b/content/reviews/books/pro-vim.md index fbc6322..48b7891 100644 --- a/content/reviews/books/pro-vim.md +++ b/content/reviews/books/pro-vim.md @@ -3,7 +3,7 @@ title = "Pro Vim - Mark McDonnell" date = 2019-09-04 [taxonomies] -tags = ["en-au", "books", "reviews", "vim", "mark mcdonnell"] +tags = ["books", "reviews", "vim", "mark mcdonnell"] +++ [GoodReads link](https://www.goodreads.com/book/show/23717582-pro-vim): (No diff --git a/content/reviews/books/programming-rust-fast-safe-systems-development.md b/content/reviews/books/programming-rust-fast-safe-systems-development.md index 8aeb424..d4e28c5 100644 --- a/content/reviews/books/programming-rust-fast-safe-systems-development.md +++ b/content/reviews/books/programming-rust-fast-safe-systems-development.md @@ -2,19 +2,41 @@ title = "Programming Rust: Fast, Safe Systems Development - Jim Blandy" date = 2018-05-22 -category = "review" - [taxonomies] -tags = ["books", "en-au", "jim blandy"] +tags = ["books", "jim blandy", "reviews", "it", "rust"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/25550614-programming-rust): +Rust is a new systems programming language that combines the performance and +low-level control of C and C++ with memory safety and thread safety. Rust's +modern, flexible types ensure your program is free of null pointer +dereferences, double frees, dangling pointers, and similar bugs, all at +compile time, without runtime overhead. In multi-threaded code, Rust catches +data races at compile time, making concurrency much easier to use. + + + {{ stars(stars=4) }} -First off, this is not a book for *learning* Rust: This is a Reference Book. A good one at it, but not for learning. +First off, this is not a book for *learning* Rust: This is a Reference Book. A +good one at it, but not for learning. -My inclination to learn Rust is how it deals with errors (it's `Result` enum), something that most languages seem to drop out of context or accept some "catch all" which let developers ignore such errors. Rust doesn't; you have to deal with errors. +My inclination to learn Rust is how it deals with errors (it's `Result` enum), +something that most languages seem to drop out of context or accept some +"catch all" which let developers ignore such errors. Rust doesn't; you +have to deal with errors. -And, in such small thing, which I thought it was very simple and straightforward... is not. The `Err` part can be very complex, specially if you want to keep in line with the rest of the system. Which is good. +And, in such small thing, which I thought it was very simple and +straightforward... is not. The `Err` part can be very complex, specially if +you want to keep in line with the rest of the system. Which is good. -Although a good book, it's not great. The explanation for generics is very convoluted and complex and doesn't help grasping the whole context -- maybe it's easier if you're already working with a language that has generics. And then, when you are almost getting how they work, they throw lifetimes in it and the confusion grows. +Although a good book, it's not great. The explanation for generics is very +convoluted and complex and doesn't help grasping the whole context -- maybe +it's easier if you're already working with a language that has generics. And +then, when you are almost getting how they work, they throw lifetimes in it +and the confusion grows. -Several topics are started and then become "beyond the scope of this book". So it just brushes some pointers at it and then completely forget about it. I, personally, would drop some of those -- it could mention that they exist -- and expanding for not being "beyond the scope of this book". \ No newline at end of file +Several topics are started and then become "beyond the scope of this book". So +it just brushes some pointers at it and then completely forget about it. I, +personally, would drop some of those -- it could mention that they exist -- +and expanding for not being "beyond the scope of this book". diff --git a/content/reviews/books/python-3-object-oriented-programming.md b/content/reviews/books/python-3-object-oriented-programming.md index 759d22b..873ea77 100644 --- a/content/reviews/books/python-3-object-oriented-programming.md +++ b/content/reviews/books/python-3-object-oriented-programming.md @@ -2,15 +2,39 @@ title = "Python 3 Object Oriented Programming - Dusty Phillips" date = 2016-04-02 -category = "review" - [taxonomies] -tags = ["books", "en-au", "dusty phillips"] +tags = ["books", "dusty phillips", "review", "python", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/8679996-python-3-object-oriented-programming): +The book begins with the very foundations of OOP and then uses practical +examples to show how to correctly implement Object Oriented Programming in +Python. Many examples are taken from real-world projects. The book focuses on +high-level design as well as the gritty details of the Python syntax. The +provided exercises inspire the reader to think about his or her own code, +rather than providing solved problems. If you're new to Object Oriented +Programming techniques, or if you have basic Python skills and wish to learn +in depth how and when to correctly apply Object Oriented Programming in +Python, this is the book for you. If you are an object-oriented programmer for +other languages, you too will find this book a useful introduction to Python, +as it uses terminology you are already familiar with. Python 2 programmers +seeking a leg up in the new world of Python 3 will also find the book +beneficial, and you need not necessarily know Python 2. + + + {{ stars(stars=5) }} -After a bunch of titles from Packt, I expected something that would be half OO, half Python 3. But I got a very happy surprise reading the book because it does really go intro OO, explaining from analysis to design to code and then slowly dwelving into Python around those topics. +After a bunch of titles from Packt, I expected something that would be half +OO, half Python 3. But I got a very happy surprise reading the book because it +does really go intro OO, explaining from analysis to design to code and then +slowly dwelving into Python around those topics. -Not only that, but instead of simply assuming his position is right, the author explores other possibilites and than moves back when something doesn't work -- kinda like _Robert C. Martin_ does in _Clean Code: A Handbook of Agile Software Craftsmanship_. +Not only that, but instead of simply assuming his position is right, the +author explores other possibilites and than moves back when something doesn't +work -- kinda like _Robert C. Martin_ does in _Clean Code: A Handbook of Agile +Software Craftsmanship_. -In the end, even after I work with Python for 5+ years, I still learnt a few more things about using Python for OO development (and really got in agreement with the author when OO isn't necessary!) \ No newline at end of file +In the end, even after I work with Python for 5+ years, I still learnt a few +more things about using Python for OO development (and really got in agreement +with the author when OO isn't necessary!) diff --git a/content/reviews/books/python-data-science-essentials-learn-the-fundamentals-of-data-science-with-python.md b/content/reviews/books/python-data-science-essentials-learn-the-fundamentals-of-data-science-with-python.md index a776966..d979c42 100644 --- a/content/reviews/books/python-data-science-essentials-learn-the-fundamentals-of-data-science-with-python.md +++ b/content/reviews/books/python-data-science-essentials-learn-the-fundamentals-of-data-science-with-python.md @@ -2,19 +2,38 @@ title = "Python Data Science Essentials - Learn the fundamentals of Data Science with Python - Alberto Boschetti" date = 2016-12-16 -category = "review" - [taxonomies] -tags = ["books", "en-au", "alberto boschetti"] +tags = ["books", "alberto boschetti", "reviews", "python", "data science", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/25527772-python-data-science-essentials---learn-the-fundamentals-of-data-science): +Key Features Quickly get familiar with data science using Python Save time - +and effort - with all the essential tools explained Create effective data +science projects and avoid common pitfalls with the help of examples and hints +dictated by experience Book Description + + + {{ stars(stars=2) }} -It's hard to explain this book, mostly because it's hard to get to whom it is targeted. +It's hard to explain this book, mostly because it's hard to get to whom it is +targeted. -Is it targeted to people that already know Machine Learning and want to learn Python? No, the book goes into lengths into some algorithms and has "easy to write, but not quite right" code to do so. +Is it targeted to people that already know Machine Learning and want to learn +Python? No, the book goes into lengths into some algorithms and has "easy to +write, but not quite right" code to do so. -Is it targeted to people that know Python but want to learn Machine Learning? No; even if some algorithms are explained in length, some aren't and there is very little "you use this when you have data like that" explanations. Actually, there is very little explanation on where an algorithm should be used. +Is it targeted to people that know Python but want to learn Machine Learning? +No; even if some algorithms are explained in length, some aren't and there is +very little "you use this when you have data like that" explanations. +Actually, there is very little explanation on where an algorithm should be +used. -Is it targeted to people that don't know Python and don't know Machine Learning and want to learn but? This is the gray area of the book: Again, the code is pretty simple and does not follow Python coding standards and the ML part is really shallow on the "when" and "why" sections. +Is it targeted to people that don't know Python and don't know Machine +Learning and want to learn but? This is the gray area of the book: Again, the +code is pretty simple and does not follow Python coding standards and the ML +part is really shallow on the "when" and "why" sections. -In the end, the book is simply an extended version of Scikit-Learn manual -- and I even have doubts if the manual isn't better because it explains when an algorithm should be used. \ No newline at end of file +In the end, the book is simply an extended version of Scikit-Learn manual -- +and I even have doubts if the manual isn't better because it explains when an +algorithm should be used. diff --git a/content/reviews/books/python-playground-geeky-projects-for-the-curious-programmer.md b/content/reviews/books/python-playground-geeky-projects-for-the-curious-programmer.md index 25ec0d7..9cd185c 100644 --- a/content/reviews/books/python-playground-geeky-projects-for-the-curious-programmer.md +++ b/content/reviews/books/python-playground-geeky-projects-for-the-curious-programmer.md @@ -2,19 +2,32 @@ title = "Python Playground: Geeky Projects for the Curious Programmer - Mahesh Venkitachalam" date = 2016-10-12 -category = "review" - [taxonomies] -tags = ["books", "en-au", "mahesh venkitachalam"] +tags = ["books", "mahesh venkitachalam", "reviews", "python", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/22978167-python-playground): +Python is a powerful programming language that's easy to learn and fun to play +with. But once you've gotten a handle on the basics, what do you do next? + + + {{ stars(stars=2) }} -When I start to not get a book, one thing I ask myself is: Am I the target audience for this book? 'Cause, you know, I may need to reflect if the book is actually good for beginners instead of people who already know the topic. +When I start to not get a book, one thing I ask myself is: Am I the target +audience for this book? 'Cause, you know, I may need to reflect if the book is +actually good for beginners instead of people who already know the topic. And here is the problem with this book: it does a bad job finding its target. -The reason is simple: the code is full of violations of PEP8, something Python beginners should not be exposed to and something expert developers get pissed. +The reason is simple: the code is full of violations of PEP8, something Python +beginners should not be exposed to and something expert developers get pissed. -Now, there is nothing wrong with your weekend projects to not follow standards -- that's perfectly acceptable. But when you have your code published in a book, you must, at least, follow the general guidelines that the community follows. +Now, there is nothing wrong with your weekend projects to not follow standards +-- that's perfectly acceptable. But when you have your code published in a +book, you must, at least, follow the general guidelines that the community +follows. -But let's throw this out of the window: is the book "good"? The answer is mostly "well...". It's not bad, but it isn't really interesting. It is merely ok. \ No newline at end of file +But let's throw this out of the window: is the book "good"? The answer is +mostly "well...". It's not bad, but it isn't really interesting. It is merely +ok. diff --git a/content/reviews/books/quatro-herois-e-um-bardo-contra-a-realidade-medieval.md b/content/reviews/books/quatro-herois-e-um-bardo-contra-a-realidade-medieval.md index d99ac88..472e6fe 100644 --- a/content/reviews/books/quatro-herois-e-um-bardo-contra-a-realidade-medieval.md +++ b/content/reviews/books/quatro-herois-e-um-bardo-contra-a-realidade-medieval.md @@ -2,13 +2,27 @@ title = "Quatro Heróis e um Bardo contra a Realidade Medieval - Rodrigo Assis Mesquita" date = 2016-10-12 -category = "review" - [taxonomies] -tags = ["books", "en-au", "rodrigo assis mesquita"] +tags = ["books", "pt-br", "rodrigo assis mesquita", "fantasia", "reviews", "fantasy"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/26137212-quatro-her-is-e-um-bardo-contra-a-realidade-medieval): +O que têm em comum um cavaleiro, um bárbaro, um mago, uma valquíria e um +bardo? Acompanhe Derick, Roderick, Broderick, Brigitte e Macedo tentando +começar uma típica aventura de resgate da Princesa, regada, se possível, a +cerveja, não hidromel. + + + {{ stars(stars=1) }} -Ok, não é nem um"livro", mas apenas uma história curta de quatro páginas. Mesmo assim, não consegue chegar no ponto onde a coisa fica realmente interessante. +Ok, não é nem um "livro", mas apenas uma história curta de quatro páginas. +Mesmo assim, não consegue chegar no ponto onde a coisa fica realmente +interessante. -Basicamente, uma mistura de jogos de RPG com... eu queria dizer Monty Python, mas as absurdices que acontecem não são do nível Monty Python, sendo muito mais cruas e sem sentido, ao ponto que a parte engraçada se perde completamente -- ok, tem uma absurdice que é realmente engraçada, mas ela é jogada de forma tão direta e vindo tão do nada que a piada se perde completamente. \ No newline at end of file +Basicamente, uma mistura de jogos de RPG com... eu queria dizer Monty Python, +mas as absurdices que acontecem não são do nível Monty Python, sendo muito +mais cruas e sem sentido, ao ponto que a parte engraçada se perde +completamente -- ok, tem uma absurdice que é realmente engraçada, mas +ela é jogada de forma tão direta e vindo tão do nada que a piada se perde +completamente. diff --git a/content/reviews/books/reactive-programming-with-javascript.md b/content/reviews/books/reactive-programming-with-javascript.md index 804cbf5..56d1972 100644 --- a/content/reviews/books/reactive-programming-with-javascript.md +++ b/content/reviews/books/reactive-programming-with-javascript.md @@ -2,25 +2,52 @@ title = "Reactive Programming with JavaScript - Jonathan Hayward" date = 2016-05-27 -category = "review" - [taxonomies] -tags = ["books", "en-au", "jonathan hayward"] +tags = ["books", "jonathan hayward", "reviews", "javascript", "reactive", "it"] +++ -{{ stars(stars=1) }} - -If I had to define this book in a single word, I'd had to go with "unfocused". -Now, with that title, you'd expect to learn about the principles that drove the design of things like "ReactJS". But it doesn't. This is not about Reactive Programming. It's about ReactJS. And it's not about Reactive Programming, it's about Reactive *Funcional* Programming. +[GoodReads Summary](https://www.goodreads.com/book/show/26202851-reactive-programming-with-javascript): +Learn the hot new front-end web framework from Facebook: ReactJS, an easy way +of developing the V in MVC and a better approach to software engineering in +JavaScript. -Well, you'd still expect it to come with some conclusions about ReactJS, right? Wrong again. + -Most of the time you'll spend reading things that have absolutely no relation with reactive programming, functional reactive programming or even ReactJS. There is a long rant about C++ which ends with no conclusion at all and gives no pointers on how it connects to the whole. There is another discussion about INTERCAL which leads to nowhere -- maybe, except, the author's bank account for the number of words. - -At some point, the author finally discusses a bit of functional programming talking about `map`, `filter` and `reduce`, but it goes nowhere from there and a whole chapter with 10+ pages have a single paragraph about real, focused talk about functional programming; the rest is just more rambling going to nowhere. - -If it was possible to run tests over the content of the book, the amount of content out of a coverage on a BDD about Reactive Programming would point that about 90% of it is never tested. It's content that talks absolutely *nothing* about reactive programming, with large portions being repeated over and over again (which makes me, once again, wonder why Packt pays for reviewers when this kind of bullshit happens). +{{ stars(stars=1) }} -"This book is about ReactJS", the author says in the introduction, but there are only 4 chapters about ReactJS, with terrible JavaScript and absolutely no explanation on *why* things are being designed that way. +If I had to define this book in a single word, I'd had to go with "unfocused". -You want a review in a single phrase? Ok, that phrase would be "stay away from this book". \ No newline at end of file +Now, with that title, you'd expect to learn about the principles that drove +the design of things like "ReactJS". But it doesn't. This is not about +Reactive Programming. It's about ReactJS. And it's not about Reactive +Programming, it's about Reactive *Funcional* Programming. + +Well, you'd still expect it to come with some conclusions about ReactJS, +right? Wrong again. + +Most of the time you'll spend reading things that have absolutely no relation +with reactive programming, functional reactive programming or even ReactJS. +There is a long rant about C++ which ends with no conclusion at all and gives +no pointers on how it connects to the whole. There is another discussion about +INTERCAL which leads to nowhere -- maybe, except, the author's bank account +for the number of words. + +At some point, the author finally discusses a bit of functional programming +talking about `map`, `filter` and `reduce`, but it goes nowhere from there and +a whole chapter with 10+ pages have a single paragraph about real, focused +talk about functional programming; the rest is just more rambling going to +nowhere. + +If it was possible to run tests over the content of the book, the amount of +content out of a coverage on a BDD about Reactive Programming would point that +about 90% of it is never tested. It's content that talks absolutely *nothing* +about reactive programming, with large portions being repeated over and over +again (which makes me, once again, wonder why Packt pays for reviewers when +this kind of bullshit happens). + +"This book is about ReactJS", the author says in the introduction, but there +are only 4 chapters about ReactJS, with terrible JavaScript and absolutely no +explanation on *why* things are being designed that way. + +You want a review in a single phrase? Ok, that phrase would be "stay away from +this book". diff --git a/content/reviews/books/ready-player-one.md b/content/reviews/books/ready-player-one.md index 547e88b..ef54541 100644 --- a/content/reviews/books/ready-player-one.md +++ b/content/reviews/books/ready-player-one.md @@ -2,23 +2,42 @@ title = "Ready Player One - Ernest Cline" date = 2015-03-24 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ernest cline"] +tags = ["books", "ernest cline", "reviews", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/9969571-ready-player-one): +IN THE YEAR 2044, reality is an ugly place. The only time teenage Wade Watts +really feels alive is when he's jacked into the virtual utopia known as the +OASIS. Wade's devoted his life to studying the puzzles hidden within this +world's digital confines, puzzles that are based on their creator's obsession +with the pop culture of decades past and that promise massive power and +fortune to whoever can unlock them. + + + {{ stars(stars=5) }} **80s, Back to Back** -First, small spoiler: imagine a world were Second Life won and reached its wildest dream. A world created by an 80s aficionado. Imagine there is a prize hidden somewhere. Imagine the locks are all based on 80s stuff. That's the book. +First, small spoiler: imagine a world were Second Life won and reached its +wildest dream. A world created by an 80s aficionado. Imagine there is a prize +hidden somewhere. Imagine the locks are all based on 80s stuff. That's the +book. -Now, if you're a children of the 80s, this will be a great ride. You'll find a bunch of stuff you remember appearing everywhere. And you'll remember what it was and it will be fun. +Now, if you're a children of the 80s, this will be a great ride. You'll find a +bunch of stuff you remember appearing everywhere. And you'll remember what it +was and it will be fun. All this you can read in all other reviews. -The story suddenly drops mid book before returning to the old 80s memorabilia trip. A couple of pages could remove one hundred and the book would be a lot more fun (and that's why I'm not giving it 5 starts). +The story suddenly drops mid book before returning to the old 80s memorabilia +trip. A couple of pages could remove one hundred and the book would be a lot +more fun (and that's why I'm not giving it 5 starts). -Some things will piss you off: the "evil" guys are one dimensional. The romance is dull. The hero never gets in a corner he doesn't find a way out. The fights are too colorful. It may not sound so, but it is annoying.... Till you realize 80s movies were just like that. +Some things will piss you off: the "evil" guys are one dimensional. The +romance is dull. The hero never gets in a corner he doesn't find a way out. +The fights are too colorful. It may not sound so, but it is annoying.... Till +you realize 80s movies were just like that. -It's really a fun book and I never knew I could read that fast. \ No newline at end of file +It's really a fun book and I never knew I could read that fast. diff --git a/content/reviews/books/redshirts.md b/content/reviews/books/redshirts.md index 0b08893..d8a1dfe 100644 --- a/content/reviews/books/redshirts.md +++ b/content/reviews/books/redshirts.md @@ -2,11 +2,18 @@ title = "Redshirts - John Scalzi" date = 2015-01-28 -category = "review" - [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "reviews", "scifi", "comedy"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/13055592-redshirts): +Ensign Andrew Dahl has just been assigned to the Universal Union Capital Ship +Intrepid, flagship of the Universal Union since the year 2456. It’s a prestige +posting, and Andrew is thrilled all the more to be assigned to the ship’s +Xenobiology laboratory. + + + {{ stars(stars=5) }} There are two simple words to describe this book: Galaxy Quest. @@ -15,12 +22,19 @@ And then, they aren't. "It's complicated", are some characters in the book say over and over again. -But the first part is. And it's too damn hilarious -- if you're a Star Trek fan, that is. Or some of the lesser sci-fi series. +But the first part is. And it's too damn hilarious -- if you're a Star Trek +fan, that is. Or some of the lesser sci-fi series. -But the story picks up every absurd psedo-science and plot twist from the series and extrapolates to the silliest level possible. I can't remember the last time a book made me laugh. +But the story picks up every absurd psedo-science and plot twist from the +series and extrapolates to the silliest level possible. I can't remember the +last time a book made me laugh. -It's silly. It's funny. It's the Galaxy Quest for every sci-fi series in the planet. +It's silly. It's funny. It's the Galaxy Quest for every sci-fi series in the +planet. -And, then, after the curtains close... It goes into a deep, touching story about... life, basically. You think you're done, but then it gets deeper and serious and... touching, basically. +And, then, after the curtains close... It goes into a deep, touching story +about... life, basically. You think you're done, but then it gets deeper and +serious and... touching, basically. -I thoroughly enjoyed reading it. And my reading statuses for this book proves it. \ No newline at end of file +I thoroughly enjoyed reading it. And my reading statuses for this book proves +it. diff --git a/content/reviews/books/rin-tin-tin-a-vida-e-a-lenda.md b/content/reviews/books/rin-tin-tin-a-vida-e-a-lenda.md index c743026..88c9b82 100644 --- a/content/reviews/books/rin-tin-tin-a-vida-e-a-lenda.md +++ b/content/reviews/books/rin-tin-tin-a-vida-e-a-lenda.md @@ -2,17 +2,70 @@ title = "Rin Tin Tin: A Vida e a Lenda - Susan Orlean" date = 2016-07-04 -category = "review" - [taxonomies] -tags = ["books", "en-au", "susan orlean"] +tags = ["books", "susan orlean", "pt-br", "biografia", "rin tin tin"] +++ + +[Resumo GoodReads](): +Ele achava que o cão era imortal. Assim começa a vasta, poderosa e comovente +narrativa de Susan Orlean sobre a jornada de Rin Tin Tin – de sobrevivente +órfão a astro do cinema e ícone internacional do showbiz. Suzan, redatora da +New Yorker chamada de “patrimônio nacional” pelo Washington Post, passou cerca +de dez anos pesquisando e escrevendo sua mais cativante obra: a história de um +cão que nasceu em 1918 e nunca morreu. A narrativa começa num campo de batalha +francês da Primeira Guerra Mundial, quando Lee Duncan, um jovem soldado +americano, descobre um sobrevivente: um pastor-alemão recém-nascido nas ruínas +de um canil bombardeado. Para Duncan, que passou parte da infância num +orfanato, a sobrevivência do cão fora um milagre. Havia algo em Rin Tin Tin +que o compelia a compartilhá-lo com o mundo. Duncan o levou, então, para a +Califórnia, onde suas aptidões físicas e a capacidade de representar chamaram +a atenção da Warner Bros. Durante os dez anos seguintes, Rinty estrelou 23 +sucessos do cinema mudo que salvaram o estúdio da falência e fizeram dele o +cão mais famoso de todos os tempos. No auge da popularidade, Rin Tin Tin foi o +campeão de bilheteria de Hollywood. Ao longo das décadas seguintes, Rinty e +seus descendentes fizeram a conturbada jornada do cinema mudo ao falado, do +preto e branco à cor, do rádio à televisão, culminando no seriado de TV As +Aventuras de Rin-Tin-Tin, um dos mais populares programas da época do baby +boom. O legado do cão herói foi consolidado por Duncan e alguns outros – como +Bert Leonard, o produtor do seriado da TV, e Daphne Hereford, a proprietária +do atual Rin Tin Tin –, que dedicaram a vida para assegurar a imortalidade da +lenda. Na essência de Rin Tin Tin – a Vida e a Lenda há um tocante estudo do +duradouro vínculo entre os humanos e os animais. Mas o livro é também uma +história ricamente matizada da indústria do entretenimento e do +empreendedorismo no século XX. Abarcando um período de 90 anos, ele aborda a +mudança de status dos cães, de ajudantes em fazendas a membros diletos das +famílias urbanas, da origem do treinamento para a obediência à evolução +genética das raças, da ascensão de Hollywood ao passado e presente dos cães de +guerra. Rico de humor e emoção, repleto de momentos que certamente levarão o +leitor às lágrimas, Rin Tin Tin fez parte da prestigiadíssima lista dos 100 +MELHORES LIVROS DO ANO do New York Times, principalmente por ser uma mescla +irresistível de história, humanismo e maestria narrativa – esplêndida +celebração de um grande ícone universal por uma das mais talentosas escritoras +da atualidade. + + + + {{ stars(stars=3) }} -Aviso: Eu nunca fui um fã de Rin Tin Tin, até porque nunca acompanhei nenhuma das séries. Mas como "cachorreiro", me senti obrigado a pegar esse livro, até porque estava em promoção. +Aviso: Eu nunca fui um fã de Rin Tin Tin, até porque nunca acompanhei nenhuma +das séries. Mas como "cachorreiro", me senti obrigado a pegar esse livro, até +porque estava em promoção. -Embora pareça que o livro irá tratar do cachorro, o contexto geral são "coisas ao redor do primeiro cachorro chamado Rin Tin Tin, que fez alguns filmes mudos e depois teve uma série de TV" -- até porque a parte da vida termina antes da metade do livro. +Embora pareça que o livro irá tratar do cachorro, o contexto geral são "coisas +ao redor do primeiro cachorro chamado Rin Tin Tin, que fez alguns filmes mudos +e depois teve uma série de TV" -- até porque a parte da vida termina antes da +metade do livro. -Um dos problemas do livro é que a autora fica, boa parte do tempo, conjecturando sobre o "produto" (por assim dizer) Rin Tin Tin do que focando nos personagens. Boa parte do livro parece uma reportagem de jornal estendida para ficar do tamanho de um livro. Também -- e aqui vou me valer do mesmo artifício e dar a minha opinião -- o livro carece um monte de imagens: para um produto visual (afinal de contas, 4 filmes e um seriado são visuais), algumas fotos dos Rin Tin Tins e seus coadjuvantes ajudaria a trazer o cachorro em evidência ao invés de ficar no produto metafísico "Rin Tin Tin". +Um dos problemas do livro é que a autora fica, boa parte do tempo, +conjecturando sobre o "produto" (por assim dizer) Rin Tin Tin do que focando +nos personagens. Boa parte do livro parece uma reportagem de jornal estendida +para ficar do tamanho de um livro. Também -- e aqui vou me valer do mesmo +artifício e dar a minha opinião -- o livro carece um monte de imagens: para um +produto visual (afinal de contas, 4 filmes e um seriado são visuais), algumas +fotos dos Rin Tin Tins e seus coadjuvantes ajudaria a trazer o cachorro em +evidência ao invés de ficar no produto metafísico "Rin Tin Tin". -No fim, ao invés de focar no cachorro, como esperado, o livro se foca no produto e seus coadjuvantes, deixando a impressão de que tudo não passou parte de um roteiro dentro do roteiro. \ No newline at end of file +No fim, ao invés de focar no cachorro, como esperado, o livro se foca no +produto e seus coadjuvantes, deixando a impressão de que tudo não passou parte +de um roteiro dentro do roteiro. diff --git a/content/reviews/books/rust-essentials.md b/content/reviews/books/rust-essentials.md index 6e9fddc..cc62b51 100644 --- a/content/reviews/books/rust-essentials.md +++ b/content/reviews/books/rust-essentials.md @@ -2,21 +2,43 @@ title = "Rust Essentials - Ivo Balbaert" date = 2015-07-02 -category = "review" - [taxonomies] -tags = ["books", "en-au", "ivo balbaert"] +tags = ["books", "ivo balbaert", "reviews", "rust", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/25644753-rust-essentials): +Discover how to use Rust to write fast, secure, and concurrent systems and +applications About This Book Learn how to create secure and blazingly fast +programs in Rust Start working with Rust in a multicore and distributed +environment Explore the core characteristics of Rust - safety, performance, +and concurrency - to build error free and robust code Who This Book Is For + + + {{ stars(stars=3) }} -Rust is a language that intrigues me. It seems it has a good deal of protections and clever structures to prevent problems that other languages have. And it usually outperforms C (at least, in the Euler tests). +Rust is a language that intrigues me. It seems it has a good deal of +protections and clever structures to prevent problems that other languages +have. And it usually outperforms C (at least, in the Euler tests). -But I really never really "got" the language just reading Rust By Example and The Rust Programming Language. So I bought this book. +But I really never really "got" the language just reading Rust By Example and +The Rust Programming Language. So I bought this book. -Sure, it goes slowly to teach you the light intricacies of the language, but it never, in any point, goes deep into it, which is really annoying. It tries to pick a subject to tell how to code in Rust (using a theoretical game), but it never completes it. You never see the final product of all the stuff it was just explained. And some examples have nothing to do with it. +Sure, it goes slowly to teach you the light intricacies of the language, but +it never, in any point, goes deep into it, which is really annoying. It tries +to pick a subject to tell how to code in Rust (using a theoretical game), but +it never completes it. You never see the final product of all the stuff it was +just explained. And some examples have nothing to do with it. -The problem with shallowness of the book gets exponentially worse when talking to complex subjects, like threading and unsafe blocks. Because it never goes too deep, you end up handing with simple threads the basically just add numbers, nothing something so complex that would actually require threads in the first place. +The problem with shallowness of the book gets exponentially worse when talking +to complex subjects, like threading and unsafe blocks. Because it never goes +too deep, you end up handing with simple threads the basically just add +numbers, nothing something so complex that would actually require threads in +the first place. -Also, it seems the book was not reviewed. There is one paragraph saying one thing (traits can't have implementations), just to, a few paragraphs later, showing exactly the opposite (like a trait with an implementation). There are two "We'll see X in the next section" with said next section just below it. +Also, it seems the book was not reviewed. There is one paragraph saying one +thing (traits can't have implementations), just to, a few paragraphs later, +showing exactly the opposite (like a trait with an implementation). There are +two "We'll see X in the next section" with said next section just below it. -It's an ok introduction to Rust, but it goes short in several places. \ No newline at end of file +It's an ok introduction to Rust, but it goes short in several places. diff --git a/content/reviews/books/scrum-a-arte-de-fazer-o-dobro-de-trabalho-na-metade-do-tempo.md b/content/reviews/books/scrum-a-arte-de-fazer-o-dobro-de-trabalho-na-metade-do-tempo.md index a1266a2..bddb0da 100644 --- a/content/reviews/books/scrum-a-arte-de-fazer-o-dobro-de-trabalho-na-metade-do-tempo.md +++ b/content/reviews/books/scrum-a-arte-de-fazer-o-dobro-de-trabalho-na-metade-do-tempo.md @@ -2,17 +2,45 @@ title = "Scrum: A arte de fazer o dobro de trabalho na metade do tempo - Jeff Sutherland" date = 2016-06-08 -category = "review" - [taxonomies] -tags = ["books", "en-au", "jeff sutherland"] +tags = ["books", "pt-br", "jeff sutherland", "ágil", "scrum", "reviews"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/25053915-scrum): +Se você já foi surpreendido por quão rápido o mundo está mudando, Scrum é uma +das razões. Para aqueles que acreditam que deve haver uma maneira mais +eficiente de se fazer as coisas, este é um livro sobre o processo de gestão +que está mudando a maneira como vivemos. Desde o advento do método, já foram +registrados ganhos de produtividade de até 1.200%. Tecida com insights de +artes marciais, tomadas de decisão judicial, combate aéreo avançado, robótica +e muitas outras disciplinas, Scrum é sempre fascinante. Seja para inventar uma +tecnologia pioneira ou para estabelecer os alicerces de prosperidade de uma +família. + + + {{ stars(stars=5) }} -Aviso: Eu já conhecia o Scrum de usar o mesmo para desenvolvimento, então certas partes já eram conhecidas. Entretanto, mesmo nesse caso, para quem já conhece a metodologia, saber o *porquê* de certas coisas é um bocado interessante. +Aviso: Eu já conhecia o Scrum de usar o mesmo para desenvolvimento, então +certas partes já eram conhecidas. Entretanto, mesmo nesse caso, para quem já +conhece a metodologia, saber o *porquê* de certas coisas é um bocado +interessante. -O começo é meio devagar, pois Sutherland fala muito de sua vida e como chegou a pensar no Scrum. Não há qualquer informação de como funciona, como proceder ou até mesmo o porquê. Pelo terceiro capítulo é que as bases do Scrum começam a ser comentadas e aí é que a coisa faz sentido. +O começo é meio devagar, pois Sutherland fala muito de sua vida e como chegou +a pensar no Scrum. Não há qualquer informação de como funciona, como proceder +ou até mesmo o porquê. Pelo terceiro capítulo é que as bases do Scrum começam +a ser comentadas e aí é que a coisa faz sentido. -O final também é um pouco de história: ao invés de continuar a explicar exatamente como funciona o scrum (ou, de novo, os seus porquês), há uma lista de projetos que usam Scrum e que não são relacionados com TI. Embora seja interessante saber que há projetos desse tipo usando a metodologia, o mesmo se torna um pouco cansativo pois, mais uma vez, não foca no scrum em si. +O final também é um pouco de história: ao invés de continuar a explicar +exatamente como funciona o scrum (ou, de novo, os seus porquês), há uma lista +de projetos que usam Scrum e que não são relacionados com TI. Embora seja +interessante saber que há projetos desse tipo usando a metodologia, o mesmo se +torna um pouco cansativo pois, mais uma vez, não foca no scrum em si. -Junto com os porquês, há, no final de cada capítulo, um pequeno resumo, que ajuda a entender melhor o processo e serve como consulta rápida na futuro. O apêndice final inclui um "Como aplicar o Scrum" que explica de forma resumida o passo a passo de iniciar um projeto scrum, com indicadores de onde encontrar maiores informações dentro do próprio livro. Ou seja, o livro não serve apenas como um "como aprender scrum", mas também possui informações suficientes para servir de referência futura. \ No newline at end of file +Junto com os porquês, há, no final de cada capítulo, um pequeno resumo, que +ajuda a entender melhor o processo e serve como consulta rápida na futuro. O +apêndice final inclui um "Como aplicar o Scrum" que explica de forma resumida +o passo a passo de iniciar um projeto scrum, com indicadores de onde encontrar +maiores informações dentro do próprio livro. Ou seja, o livro não serve apenas +como um "como aprender scrum", mas também possui informações suficientes para +servir de referência futura. diff --git a/content/reviews/books/seven-languages-in-seven-weeks.md b/content/reviews/books/seven-languages-in-seven-weeks.md index 4692a2d..0211d4c 100644 --- a/content/reviews/books/seven-languages-in-seven-weeks.md +++ b/content/reviews/books/seven-languages-in-seven-weeks.md @@ -3,10 +3,10 @@ title = "Seven Languages in Seven Weeks" date = 2019-07-16 [taxonomies] -tags = ["books", "reviews", "en-au", "bruce a tate", "clojure", "haskell", "io", "prolog", "scala", "erlang", "ruby"] +tags = ["books", "reviews", "bruce a tate", "clojure", "haskell", "io", "prolog", "scala", "erlang", "ruby", "it"] +++ -[Goodreads summary](https://www.goodreads.com/book/show/7912517-seven-languages-in-seven-weeks): +[GoodReads summary](https://www.goodreads.com/book/show/7912517-seven-languages-in-seven-weeks): You should learn a programming language every year, as recommended by The Pragmatic Programmer. But if one per year is good, how about Seven Languages in Seven Weeks? In this book you'll get a hands-on tour of Clojure, Haskell, diff --git a/content/reviews/books/silence-on-the-wire-a-field-guide-to-passive-reconnaissance-and-indirect-attacks.md b/content/reviews/books/silence-on-the-wire-a-field-guide-to-passive-reconnaissance-and-indirect-attacks.md index 9b22f07..37cd4e1 100644 --- a/content/reviews/books/silence-on-the-wire-a-field-guide-to-passive-reconnaissance-and-indirect-attacks.md +++ b/content/reviews/books/silence-on-the-wire-a-field-guide-to-passive-reconnaissance-and-indirect-attacks.md @@ -2,17 +2,39 @@ title = "Silence on the Wire: A Field Guide to Passive Reconnaissance and Indirect Attacks - Michal Zalewski" date = 2016-06-23 -category = "review" - [taxonomies] -tags = ["books", "en-au", "michal zalewski"] +tags = ["books", "michal zalewski", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/82994.Silence_on_the_Wire): +There are many ways that a potential attacker can intercept information, or +learn more about the sender, as the information travels over a network. +Silence on the Wire uncovers these silent attacks so that system +administrators can defend against them, as well as better understand and +monitor their systems. + + + {{ stars(stars=2) }} -This is a book about passive detection. Or active detection. Or attacks. I really don't know, because the subject keeps jumping around so much you have no idea the point the author wants to make. +This is a book about passive detection. Or active detection. Or attacks. I +really don't know, because the subject keeps jumping around so much you have +no idea the point the author wants to make. -There are plenty explanations for stuff, but mostly is dumbed down to the point it doesn't even make sense. Besides that, you have explanations for attacks that sounds really scary/cool (depending on your point of view) but after you think a bit about it, it is really hard to execute and, with the necessary access to do so, you wouldn't really need this kind of stuff. +There are plenty explanations for stuff, but mostly is dumbed down to the +point it doesn't even make sense. Besides that, you have explanations for +attacks that sounds really scary/cool (depending on your point of view) but +after you think a bit about it, it is really hard to execute and, with the +necessary access to do so, you wouldn't really need this kind of stuff. -Also, there is plenty of "this author research" or "a research that yours truly did" that sounds more like "Hey, look how awesome I am" than "you should really worry about this thing". +Also, there is plenty of "this author research" or "a research that yours +truly did" that sounds more like "Hey, look how awesome I am" than "you should +really worry about this thing". -About the edition, there are original articles in their original form, but they are presented in mono spaced font in a weird indentation that doesn't fit any layout you chose (landscape, two columns landscape, portrait). Also, there are chapter footnotes and book footnotes and both follow the same format, which means you will find a "[1]", followed by a "[100]", followed by a "[2]". And the author uses "Too," instead of "Also," which, for a non-native English speaking person like me, sounds strange as hell. \ No newline at end of file +About the edition, there are original articles in their original form, but +they are presented in mono spaced font in a weird indentation that doesn't fit +any layout you chose (landscape, two columns landscape, portrait). Also, there +are chapter footnotes and book footnotes and both follow the same format, +which means you will find a "[1]", followed by a "[100]", followed by a "[2]". +And the author uses "Too," instead of "Also," which, for a non-native English +speaking person like me, sounds strange as hell. diff --git a/content/reviews/books/soulminder.md b/content/reviews/books/soulminder.md index faea5b8..11dbd69 100644 --- a/content/reviews/books/soulminder.md +++ b/content/reviews/books/soulminder.md @@ -3,7 +3,7 @@ title = "Soulminder - Timothy Zahn" date = 2018-12-13 [taxonomies] -tags = ["books", "en-au", "timothy zahn", "sci-fi"] +tags = ["books", "timothy zahn", "scifi", "reviews"] +++ [GoodReads summary](https://www.goodreads.com/book/show/21822375-soulminder): diff --git a/content/reviews/books/storm-real-time-processing-cookbook.md b/content/reviews/books/storm-real-time-processing-cookbook.md index e06fc99..ef78a60 100644 --- a/content/reviews/books/storm-real-time-processing-cookbook.md +++ b/content/reviews/books/storm-real-time-processing-cookbook.md @@ -2,15 +2,31 @@ title = "Storm Real-Time Processing Cookbook - Quinton Anderson" date = 2017-07-30 -category = "review" - [taxonomies] -tags = ["books", "en-au", "quinton anderson"] +tags = ["books", "quinton anderson", "reviews", "it", "storm", "stream processing", "big data"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18430542-storm-real-time-processing-cookbook): +A Cookbook with plenty of practical recipes for different uses of Storm.If you +are a Java developer with basic knowledge of real-time processing and would +like to learn Storm to process unbounded streams of data in real time, then +this book is for you. + + + {{ stars(stars=2) }} -The book presents a couple of problems and how to solve them in Storm. Or, at least, that's the premise. +The book presents a couple of problems and how to solve them in Storm. Or, at +least, that's the premise. -The whole problem is that the problem is described in very high level, like "process the logs". While this sounds alright, the book never goes to explain *how* the logs are store, they format and so on. So you have a solution for a very high level which you have no idea how good the solution could be because you have no idea how the data exists. It simply does and the Storm topology process it and that's it. +The whole problem is that the problem is described in very high level, like +"process the logs". While this sounds alright, the book never goes to explain +*how* the logs are store, they format and so on. So you have a solution for a +very high level which you have no idea how good the solution could be because +you have no idea how the data exists. It simply does and the Storm topology +process it and that's it. -Another problem is that, because all solutions are written in Java and Java is too damn verbose, instead of showing the whole code, the book goes into "Go to the file X, use the IDE to automatically add the imports and add this function." You never get a clear picture of how a complete bolt looks like. \ No newline at end of file +Another problem is that, because all solutions are written in Java and Java is +too damn verbose, instead of showing the whole code, the book goes into "Go to +the file X, use the IDE to automatically add the imports and add this +function." You never get a clear picture of how a complete bolt looks like. diff --git a/content/reviews/books/subterranean-scalzi-super-bundle.md b/content/reviews/books/subterranean-scalzi-super-bundle.md index 3f7df4d..ac8c831 100644 --- a/content/reviews/books/subterranean-scalzi-super-bundle.md +++ b/content/reviews/books/subterranean-scalzi-super-bundle.md @@ -2,27 +2,61 @@ title = "Subterranean Scalzi Super Bundle - John Scalzi" date = 2015-03-20 -category = "review" - [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "reviews", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/16157467-subterranean-scalzi-super-bundle): + +Subterranean Press bundles together all of their John Scalzi titles into one easy-to-buy special this November: + +How I Proposed To My Wife: An Alien Sex Story + +An Election + +Judge Sn Goes Golfing + +Questions for a Soldier + +The Sagan Diary + +The Tale of the Wicked + +The God Engines + +You're Not fooling Anyone When You Take Your Laptop to the Coffee Shop + + + + {{ stars(stars=3) }} **the stories are good, the blog posts, not so much** This is a book on five acts. -The first act you have the stories. In this act, "The Diary of Jane Sagan" and "God Machines" are going to get stuck in your head, 'cause they are pretty excellent stories. +The first act you have the stories. In this act, "The Diary of Jane Sagan" and +"God Machines" are going to get stuck in your head, 'cause they are pretty +excellent stories. The second act are blog posts, which are meh. The third act is a single story, which is ok. -The fourth act are more blog posts, which manages to be more Boeing than the ones in the second act. +The fourth act are more blog posts, which manages to be more Boeing than the +ones in the second act. -The fifth act are unused chapters from "Lock In". They are probably good, if you read the published story. +The fifth act are unused chapters from "Lock In". They are probably good, if +you read the published story. -Now, while the stories are good, the fact that 70% of the book are blog posts is a real let down, mostly because I think blog posts are boring. Sure, there are exceptions to this rule, like Wil Weathon's book, in which he just don't put the posts, but actually put some background about them. For Scalzi, there is no such reflections and most of the posts are not even interesting, 'cause they are temporal or regional (like elections and things related to the USA). After a while, I just skipped most of them. +Now, while the stories are good, the fact that 70% of the book are blog posts +is a real let down, mostly because I think blog posts are boring. Sure, there +are exceptions to this rule, like Wil Weathon's book, in which he just don't +put the posts, but actually put some background about them. For Scalzi, there +is no such reflections and most of the posts are not even interesting, 'cause +they are temporal or regional (like elections and things related to the USA). +After a while, I just skipped most of them. -Is it a worth book? Hard to answer. If I had only the stories and no blog posts, that would be awesome, but the posts just make the book longer without the need for such. \ No newline at end of file +Is it a worth book? Hard to answer. If I had only the stories and no blog +posts, that would be awesome, but the posts just make the book longer without +the need for such. diff --git a/content/reviews/books/tecnicas-de-memorizacao-para-estudantes-porque-voce-pode-ir-alem.md b/content/reviews/books/tecnicas-de-memorizacao-para-estudantes-porque-voce-pode-ir-alem.md index 9146a89..781e39c 100644 --- a/content/reviews/books/tecnicas-de-memorizacao-para-estudantes-porque-voce-pode-ir-alem.md +++ b/content/reviews/books/tecnicas-de-memorizacao-para-estudantes-porque-voce-pode-ir-alem.md @@ -2,15 +2,32 @@ title = "Tecnicas de Memorizacao Para Estudantes: Porque Voce Pode IR Alem - Rodrigo Vargas" date = 2016-03-14 -category = "review" - [taxonomies] -tags = ["books", "en-au", "rodrigo vargas"] +tags = ["books", "pt-br", "rodrigo vargas", "reviews", "memória"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/38092282-tecnicas-de-memorizacao-para-estudantes): +Cansado de estudar...estudar...e na hora da prova dar branco? Pois e...Eu +mesmo passei por isso diversas vezes na minha vida estudantil. Mas essa +experiencia me proporcionou a oportunidade de pesquisar e buscar entender o +processo da memorizacao e as tecnicas que podem fixar com muito mais qualidade +e eficacia o conteudo da materia estudada. Isto resultou no primeiro livro, +ainda em 1993, e de la para ca, a edicao foi revista e ampliada. Eu realmente +gostaria de ter tido acesso a essas informacoes quando era estudante. Mas +voce, hoje, tem essa informacao disponivel. Faca como milhares de outros +estudantes e conheca essas tecnicas simples e eficazes, para melhorar sua +capacidade de memorizacao. + + + {{ stars(stars=2) }} -É difícil fazer um review de um livro de memorização sem ter algo para memorizar no momento, mas enfim... +É difícil fazer um review de um livro de memorização sem ter algo para +memorizar no momento, mas enfim... -O livro trás três técnicas para memorizar coisas: reler, utilizar mnemônicos e associação de imagens mentais. Nenhuma delas é explorada a fundo (mnemônicos até nem precisa tanto) e 50% do livro é perdido falando como descobrir o dia da semana de qualquer ano. +O livro trás três técnicas para memorizar coisas: reler, utilizar mnemônicos e +associação de imagens mentais. Nenhuma delas é explorada a fundo (mnemônicos +até nem precisa tanto) e 50% do livro é perdido falando como descobrir o dia +da semana de qualquer ano. -Simples, direto e superficial. É como preciso descrever esse livro. \ No newline at end of file +Simples, direto e superficial. É como preciso descrever esse livro. diff --git a/content/reviews/books/the-big-bad-book-of-bill-murray-a-critical-appreciation-of-the-worlds-finest-actor.md b/content/reviews/books/the-big-bad-book-of-bill-murray-a-critical-appreciation-of-the-worlds-finest-actor.md index b50df7e..8e2db46 100644 --- a/content/reviews/books/the-big-bad-book-of-bill-murray-a-critical-appreciation-of-the-worlds-finest-actor.md +++ b/content/reviews/books/the-big-bad-book-of-bill-murray-a-critical-appreciation-of-the-worlds-finest-actor.md @@ -2,27 +2,64 @@ title = "The Big Bad Book of Bill Murray: A Critical Appreciation of the World's Finest Actor - Robert Schnakenberg" date = 2018-06-03 -category = "review" - [taxonomies] -tags = ["books", "en-au", "robert schnakenberg"] +tags = ["books", "robert schnakenberg", "bill murray", "cinema", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/23995466-the-big-bad-book-of-bill-murray): +The man. The movies. The life. The legend. He’s played a deranged +groundskeeper, a bellowing lounge singer, a paranormal exterminator, and a +grouchy weatherman. He is William James “Bill” Murray, America’s greatest +national treasure. From his childhood lugging golf bags at a country club to +his first taste of success on Saturday Night Live, from his starring roles in +Hollywood blockbusters to his reinvention as a hipster icon for the +twenty-first century, The Big Bad Book of Bill Murray chronicles every aspect +of his extraordinary life and career. + + + {{ stars(stars=2) }} -There are real biographies and biographies written by fans. This falls in the second, which means it's not a good biography. +There are real biographies and biographies written by fans. This falls in the +second, which means it's not a good biography. -Here is the thing: biographies should focus on which kind of person the subject really is: Are they a good person or a bad person? Are they nice or are they assholes? And there is no exact answer for this, 'cause people can be nice sometimes and assholes sometimes. And you have to focus on those two; if you don't, you give a half-piece of who the person really is. +Here is the thing: biographies should focus on which kind of person the +subject really is: Are they a good person or a bad person? Are they nice or +are they assholes? And there is no exact answer for this, 'cause people can be +nice sometimes and assholes sometimes. And you have to focus on those two; if +you don't, you give a half-piece of who the person really is. -And here is the problem with the book: Because it was written by a Murray fan, everything he does is written in a way to give him a good light. He fights on the backstage? The other actors had an issue with him, not that he had a problem. +And here is the problem with the book: Because it was written by a Murray fan, +everything he does is written in a way to give him a good light. He fights on +the backstage? The other actors had an issue with him, not that he had a +problem. -One such example is when the book discusses his divorces. On the second, it's not that Murray spent too much time away from home or wasn't lovingly; it was his wife asking divorce for "abandonment and physical assault". So the author didn't say Murray left his wife and, when together, used to beat her; *she said* he abandoned her and *she said* he beat her. By removing him, it turned a bad pair of actions into a passive description of Murray. +One such example is when the book discusses his divorces. On the second, it's +not that Murray spent too much time away from home or wasn't lovingly; it was +his wife asking divorce for "abandonment and physical assault". So the author +didn't say Murray left his wife and, when together, used to beat her; *she +said* he abandoned her and *she said* he beat her. By removing him, it turned +a bad pair of actions into a passive description of Murray. -The same goes with everything "bad" that could be said about him (like the cited fights with other actors/actresses). And, in the end, it puts such quotes like "I never had a fight with someone that didn't deserve", just to clean up his slate. +The same goes with everything "bad" that could be said about him (like the +cited fights with other actors/actresses). And, in the end, it puts such +quotes like "I never had a fight with someone that didn't deserve", just to +clean up his slate. -Another example of fandom: There is only *one* movie in which Murray is a bad actor -- a movie with a completely disagree with the author of the book, "Scrooged". Everything else is cited as "a mess of a movie, but Murray gives a much needed appearance" as if Murray appearance was the only redeeming fact of every movie he appeared which bombed. +Another example of fandom: There is only *one* movie in which Murray is a bad +actor -- a movie with a completely disagree with the author of the book, +"Scrooged". Everything else is cited as "a mess of a movie, but Murray gives a +much needed appearance" as if Murray appearance was the only redeeming fact of +every movie he appeared which bombed. -And this is just my tip for you, new reader: Read it with a gain of salt, as this is written by a fan who don't want to see Murray in a bad light. +And this is just my tip for you, new reader: Read it with a gain of salt, as +this is written by a fan who don't want to see Murray in a bad light. -Apart from all of this, it's a curious book 'cause, instead of going in chronological order, it goes in alphabetical order. Yeah, you read that right: Instead of going through the life events of Bill Murray, the book focus on things and people and movies in Bill's life: So every person who worked with him (maybe a few missing here), every movie made and declined, every sketch character, every family member, everything is there, in alphabetical order. +Apart from all of this, it's a curious book 'cause, instead of going in +chronological order, it goes in alphabetical order. Yeah, you read that right: +Instead of going through the life events of Bill Murray, the book focus on +things and people and movies in Bill's life: So every person who worked with +him (maybe a few missing here), every movie made and declined, every sketch +character, every family member, everything is there, in alphabetical order. -But even with this nonsensical ordering -- which is a good match for the portrait of Murray the book wants to give -- it is, still, in the very deep, a fan book which tries to make the subject seem much better than they actually are. \ No newline at end of file +But even with this nonsensical ordering -- which is a good match for the portrait of Murray the book wants to give -- it is, still, in the very deep, a fan book which tries to make the subject seem much better than they actually are. diff --git a/content/reviews/books/the-book-of-kells.md b/content/reviews/books/the-book-of-kells.md index 502f776..747e110 100644 --- a/content/reviews/books/the-book-of-kells.md +++ b/content/reviews/books/the-book-of-kells.md @@ -2,17 +2,35 @@ title = "The Book of Kells - R.A. MacAvoy" date = 2018-08-13 -category = "review" - [taxonomies] -tags = ["books", "en-au", "r.a. macavoy"] +tags = ["books", "r.a. macavoy", "reviews", "fantasy"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/941468.The_Book_of_Kells): +An unusual and original work of fantasy from the acclaimed author of Tea with +the Black Dragon. A contemporary man, John Thornburn (a meek, non-violent and +unpredictable artist) and woman, Derval (his tough, confrontational, strong +and warrior-like lover) time travel to ancient Ireland to avenge a Viking +attack. Packed with fascinating details of historical time and place in Irish +history and delicately balanced on the border between realism and fantasy, the +story centers around one of the most famous and beautiful illuminated +manuscripts in history, the legendary but entirely real Book of Kells. Celtic +history blends with magical fantasy for a strange and immersive tale of +adventure. + + + {{ stars(stars=2) }} I really don't know how to categorize this book. -I mean, for a while, I thought it was a serious fantasy book. Then things got way crazy and I thought it was a comedy. Exactly at that point, craziness went out and things were not funny anymore. +I mean, for a while, I thought it was a serious fantasy book. Then things got +way crazy and I thought it was a comedy. Exactly at that point, craziness went +out and things were not funny anymore. -Maybe the guy just read too much Irish tales and decided to write about it, since there are very few books in which the story happens in Ireland. +Maybe the guy just read too much Irish tales and decided to write about it, +since there are very few books in which the story happens in Ireland. -In the end, sure, it's a story around some Irish tales, based on Irish history and, basically, that. It's crazy, it's hard to follow and jumps around too much. \ No newline at end of file +In the end, sure, it's a story around some Irish tales, based on Irish history +and, basically, that. It's crazy, it's hard to follow and jumps around too +much. diff --git a/content/reviews/books/the-book-of-skulls.md b/content/reviews/books/the-book-of-skulls.md index 36e9228..487b4d2 100644 --- a/content/reviews/books/the-book-of-skulls.md +++ b/content/reviews/books/the-book-of-skulls.md @@ -2,29 +2,45 @@ title = "The Book of Skulls - Robert Silverberg" date = 2018-09-03 -category = "review" - [taxonomies] -tags = ["books", "en-au", "robert silverberg"] +tags = ["books", "robert silverberg", "review", "horror"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/219107.The_Book_of_Skulls): +Seeking the immortality promised in an ancient manuscript, The Book of Skulls, +four friends, college roommates, go on a spring break trip to Arizona: Eli, +the scholar, who found and translated the book; Timothy, scion of an American +dynasty, born and bred to lead; Ned, poet and cynic; and Oliver, the brilliant +farm boy obsessed with death. + + + {{ stars(stars=1) }} -The story of four friends that go after some mysterious book -- said "Book of Skulls" -- which tells about the secret for eternal life, but it requires four people, one which must be "removed" by the group and another that must be "removed" by themselves. +The story of four friends that go after some mysterious book -- said "Book of +Skulls" -- which tells about the secret for eternal life, but it requires four +people, one which must be "removed" by the group and another that must be +"removed" by themselves. But that's not the horror of it. The horror is a full paragraph of 5 pages. -The horror is each chapter being in the view of each of the four friends, but they all think exactly the same way. +The horror is each chapter being in the view of each of the four friends, but +they all think exactly the same way. -The horror is the the idea of one removed by the group and another by themselves is never actually explored. +The horror is the idea of one removed by the group and another by themselves +is never actually explored. The horror is that the resolution is predicable for miles. -The horror is a bunch of text copy'n'pasted over and over, like the author was being paid by the word. +The horror is a bunch of text copy'n'pasted over and over, like the author was +being paid by the word. -The horror is the amount of inane stories of some of the friends' past, which add absolutely nothing to the story or for building the character personalities. +The horror is the amount of inane stories of some of the friends' past, which +add absolutely nothing to the story or for building the character +personalities. The horror is the talks about sex like a horny teenage. -The whole book is the horror, not the story it contains. \ No newline at end of file +The whole book is the horror, not the story it contains. diff --git a/content/reviews/books/the-complete-collection.md b/content/reviews/books/the-complete-collection.md index 7829c03..55135f8 100644 --- a/content/reviews/books/the-complete-collection.md +++ b/content/reviews/books/the-complete-collection.md @@ -2,29 +2,71 @@ title = "The Complete Collection - H.P. Lovecraft" date = 2014-11-29 -category = "review" - [taxonomies] -tags = ["books", "en-au", "h.p. lovecraft"] +tags = ["books", "h.p. lovecraft", "reviews", "horror"] +++ + +[GoodReads Summary](): +The weird fiction short stories of H.P. Lovecraft from 1917-1935. Excludes +collaborations. + +The eBook’s table of contents is listed below. It includes the year each story +was written. + + + {{ stars(stars=1) }} -I'll spoil my impressions of this book with two phrases, which will surely make some Lovecraft fans really angry: +I'll spoil my impressions of this book with two phrases, which will surely +make some Lovecraft fans really angry: 1. Lovecraft loved to write, but not tell stories. 2. Lovecraft got paid by the word, and he really liked the money. -But before you come with pitchforks and torches to get me, let me explain the whole affair. +But before you come with pitchforks and torches to get me, let me explain the +whole affair. -First off, the first story of the book is "At the Mountains of Madness" (because all stories are in their alphabetical order) and it really rubbed me in the wrong way: It does a good job setting the ambient for the story but when it reaches its crux, it starts to dragging down and the story pace goes really *really* slow, because at this point, Lovecraft decides that almost all -- if not all -- substantives must have a proper adjective. This doesn't help the pace at all. It's like a murder scene, when the murderer appears behind the poor girl and slowly walks towards her, except he's on the other side of the house and the whole thing is in slow motion. At the end, you start to hope that the murderer runs and kills the girl already, because the suspense is already over and the thing is already dragging itself out. +First off, the first story of the book is "At the Mountains of Madness" +(because all stories are in their alphabetical order) and it really rubbed me +in the wrong way: It does a good job setting the ambient for the story but +when it reaches its crux, it starts to dragging down and the story pace goes +really *really* slow, because at this point, Lovecraft decides that almost all +-- if not all -- substantives must have a proper adjective. This doesn't help +the pace at all. It's like a murder scene, when the murderer appears behind +the poor girl and slowly walks towards her, except he's on the other side of +the house and the whole thing is in slow motion. At the end, you start to hope +that the murderer runs and kills the girl already, because the suspense is +already over and the thing is already dragging itself out. -"But that's just ONE story!" you may cry. I agree with you in that, except the pattern appears everywhere. "Nameless sound", "sinister with latent horror", "clock's abnormal ticking". It goes on and on and on, apparently trying to scare you with adjectives instead of the story itself. There are so many of those dragging the pace down that I felt asleep more than once reading the book. Yes, you read it right: A book about horror stories put me to sleep. Also, it was the first time in my whole life that I got tired of reading; no, I didn't got mentally exhausted, I didn't get physically tired; I got *tired of reading*. It was the opposite of what I felt when I finished reading "Lord of the Rings": When the story ended, I wanted to read more; with Lovecraft, I wanted to read *less*. +"But that's just ONE story!" you may cry. I agree with you in that, except the +pattern appears everywhere. "Nameless sound", "sinister with latent horror", +"clock's abnormal ticking". It goes on and on and on, apparently trying to +scare you with adjectives instead of the story itself. There are so many of +those dragging the pace down that I felt asleep more than once reading the +book. Yes, you read it right: A book about horror stories put me to sleep. +Also, it was the first time in my whole life that I got tired of reading; no, +I didn't got mentally exhausted, I didn't get physically tired; I got *tired +of reading*. It was the opposite of what I felt when I finished reading "Lord +of the Rings": When the story ended, I wanted to read more; with Lovecraft, I +wanted to read *less*. -Also, in general, Lovecraft managed to create his own little universe where his stories float around. Most authors would get this universe and expand it further and further, but Lovecraft manages to make the incredible feature of never expanding the universe, to the point that more stories actually *diminish* the universe instead of expanding it. +Also, in general, Lovecraft managed to create his own little universe where +his stories float around. Most authors would get this universe and expand it +further and further, but Lovecraft manages to make the incredible feature of +never expanding the universe, to the point that more stories actually +*diminish* the universe instead of expanding it. -Not only the stories are not superb, but the editing leaves a lot to be desired. There are two or three stories written by Lovecraft in his childhood/early teens, which seem to be added to tell that Lovecraft loved to write since the early ages, but they are put without any editing or even grammatical checking, which does more harm to the author than help him. +Not only the stories are not superb, but the editing leaves a lot to be +desired. There are two or three stories written by Lovecraft in his +childhood/early teens, which seem to be added to tell that Lovecraft loved to +write since the early ages, but they are put without any editing or even +grammatical checking, which does more harm to the author than help him. -Not that all stories are bad, some are good. But they are drowned in the world of stories that go nowhere that they are the exception instead of the rule. +Not that all stories are bad, some are good. But they are drowned in the world +of stories that go nowhere that they are the exception instead of the rule. -In the end, you can think of this: You have heard about "Necronomicon", you probably heard about "Cthulu", you may have heard about the "Old Ones" -- and that's probably it. Of about 2000 pages of stories and a lot more words, only 4 got beyond Lovecraft stories. \ No newline at end of file +In the end, you can think of this: You have heard about "Necronomicon", you +probably heard about "Cthulu", you may have heard about the "Old Ones" -- and +that's probably it. Of about 2000 pages of stories and a lot more words, only +4 got beyond Lovecraft stories. diff --git a/content/reviews/books/the-cyberiad.md b/content/reviews/books/the-cyberiad.md index 91e7ecf..e5cdbd9 100644 --- a/content/reviews/books/the-cyberiad.md +++ b/content/reviews/books/the-cyberiad.md @@ -2,19 +2,37 @@ title = "The Cyberiad - Stanisław Lem" date = 2018-09-14 -category = "review" - [taxonomies] -tags = ["books", "en-au", "stanislaw lem"] +tags = ["books", "stanislaw lem", "reviews", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18194.The_Cyberiad): +A brilliantly funny collection of stories for the next age, from the +celebrated author of Solaris. Ranging from the prophetic to the surreal, these +stories demonstrate Stanislaw Lem's vast talent and remarkable ability to +blend meaning and magic into a wholly entertaining and captivating work. + + + {{ stars(stars=3) }} -What would happen if _Isaac Asimov_ and _Douglas Adams_ had a child? Stanislaw Lem. +What would happen if _Isaac Asimov_ and _Douglas Adams_ had a child? Stanislaw +Lem. -Ok, maybe I'm pushing the story a bit too far, 'cause that's the only book I've read from Lem so far, but the stories in this book really do seem a mix between what Asimov wrote with the nonsensical humour of Adams. +Ok, maybe I'm pushing the story a bit too far, 'cause that's the only book +I've read from Lem so far, but the stories in this book really do seem a mix +between what Asimov wrote with the nonsensical humour of Adams. -The book revolves around stories of two "constructors", Trurl and Klaupacius and their adventures. And I put "constructores" with quotes 'cause, only by reading the synopsis is that I got that they were robots -- a thing the book never transpires, in a way that I thought, till now, that they were humans in a world were robots and humans live along. Good, bad? I can't say it. +The book revolves around stories of two "constructors", Trurl and Klaupacius +and their adventures. And I put "constructores" with quotes 'cause, only by +reading the synopsis is that I got that they were robots -- a thing the book +never transpires, in a way that I thought, till now, that they were humans in +a world were robots and humans live along. Good, bad? I can't say it. -While the humour is there -- and I truly appreciate Adams style and reckon the hard work of the translators -- some pieces get too long and too nonsensical to be actually funny. It becomes a chore, sometimes, to read very long paragraphs, with a bunch of weird words (cause there is a bunch of made up words, like mixing "sarcastic" and "transistor" into a single word). +While the humour is there -- and I truly appreciate Adams style and reckon the +hard work of the translators -- some pieces get too long and too nonsensical +to be actually funny. It becomes a chore, sometimes, to read very long +paragraphs, with a bunch of weird words (cause there is a bunch of made up +words, like mixing "sarcastic" and "transistor" into a single word). -It's fun overall, but not Adams fun. \ No newline at end of file +It's fun overall, but not Adams fun. diff --git a/content/reviews/books/the-drawing-of-the-three-the-dark-tower-2.md b/content/reviews/books/the-drawing-of-the-three-the-dark-tower-2.md index 7d5c837..9cf70e3 100644 --- a/content/reviews/books/the-drawing-of-the-three-the-dark-tower-2.md +++ b/content/reviews/books/the-drawing-of-the-three-the-dark-tower-2.md @@ -2,17 +2,28 @@ title = "The Drawing of the Three (The Dark Tower, #2) - Stephen King" date = 2017-08-20 -category = "review" - [taxonomies] -tags = ["books", "en-au", "stephen king"] +tags = ["books", "stephen king", "reviews", "the dark tower", "fantasy"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/5094.The_Drawing_of_the_Three): +While pursuing his quest for the Dark Tower through a world that is a +nightmarishly distorted mirror image of our own, Roland, the last gunslinger, +encounters three mysterious doorways on the beach. Each one enters into the +life of a different person living in contemporary New York. + + + {{ stars(stars=5) }} -While _The Gunslinger_ where more of "the movie that started the series" (as I put in the previous book review), this feels more like a complete book. +While _The Gunslinger_ where more of "the movie that started the series" (as I +put in the previous book review), this feels more like a complete book. Way less backstories, a lot more straight stories. -The series is still in the build up: Instead of talking directly about the tower, the book is more about the companions Roland get in the way to the tower (kinda like Jake in the previous book). +The series is still in the build up: Instead of talking directly about the +tower, the book is more about the companions Roland get in the way to the +tower (kinda like Jake in the previous book). -Still, compared to the previous book in the series, this one feel a lot more "complete" and centered around itself. \ No newline at end of file +Still, compared to the previous book in the series, this one feel a lot more +"complete" and centered around itself. diff --git a/content/reviews/books/the-drift-wars.md b/content/reviews/books/the-drift-wars.md index ea0a03e..a134841 100644 --- a/content/reviews/books/the-drift-wars.md +++ b/content/reviews/books/the-drift-wars.md @@ -2,19 +2,39 @@ title = "The Drift Wars - Brett James" date = 2015-02-03 -category = "review" - [taxonomies] -tags = ["books", "en-au", "brett james"] +tags = ["books", "brett james", "reviews", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18188712-the-drift-wars): +Peter Garvey was just a kid when the warships emerged from the Drift and +devastated his homeworld. He enlisted immediately, leaving behind his +small-town life to fight in distant space. + +Barely surviving basic training, he is thrust to the front line to battle the +Riel, an army of creatures beyond his darkest nightmares. + + + {{ stars(stars=3) }} -There are very few books that I've read that made my head spin by being so terrible describing action scenes. There is _Neuromancer_ has pretty damn good action sequences. This one, no. +There are very few books that I've read that made my head spin by being so +terrible describing action scenes. There is _Neuromancer_ has pretty damn good +action sequences. This one, no. -Maybe it's because you can't really get the pace of the sequence. Maybe it's because it's badly described. Maybe it's because things sound so cartoonish you can't really go. I mean, how can I imagine an action sequence when the big bad guy seems to be a Spidermon from Doom on steroids, the middle guys felt like Carnage from Spiderman and the mind-guys seemed copies of Mordin from Mass Effect. +Maybe it's because you can't really get the pace of the sequence. Maybe it's +because it's badly described. Maybe it's because things sound so cartoonish +you can't really go. I mean, how can I imagine an action sequence when the big +bad guy seems to be a Spidermon from Doom on steroids, the middle guys felt +like Carnage from Spiderman and the mind-guys seemed copies of Mordin from +Mass Effect. -And let's not forget the main plot machine, which makes absolutely no sense at all -- even if it's a pretty damn concept to keep the story flowing. +And let's not forget the main plot machine, which makes absolutely no sense at +all -- even if it's a pretty damn concept to keep the story flowing. -Speaking of flowing, if you take the heavy packed sequences and the enemies description, it's a pretty damn good book. Almost like "All You Need Is Kill" in structure and plot advancement. +Speaking of flowing, if you take the heavy packed sequences and the enemies +description, it's a pretty damn good book. Almost like "All You Need Is Kill" +in structure and plot advancement. -So it's not a bad book at all, and may feel like a really good read if you managed to follow Neuromancer sequences. \ No newline at end of file +So it's not a bad book at all, and may feel like a really good read if you +managed to follow Neuromancer sequences. diff --git a/content/reviews/books/the-emperors-soul.md b/content/reviews/books/the-emperors-soul.md index f3bb645..4d39c7f 100644 --- a/content/reviews/books/the-emperors-soul.md +++ b/content/reviews/books/the-emperors-soul.md @@ -2,15 +2,25 @@ title = "The Emperor's Soul - Brandon Sanderson" date = 2018-01-21 -category = "review" - [taxonomies] -tags = ["books", "en-au", "brandon sanderson"] +tags = ["books", "brandon sanderson", "review", "fantasy"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/13578175-the-emperor-s-soul): +A heretic thief is the empire’s only hope in this fascinating tale that +inhabits the same world as the popular novel, Elantris. + + + {{ stars(stars=2) }} -I got this book from a Humble Bundle of Scifi/Fantasy. It fits in the later than in the former. +I got this book from a Humble Bundle of Scifi/Fantasy. It fits in the later +than in the former. -The biggest problem I found was that the story starts midway. Surely, this is not something new, as other books take the same approach and then, slowly, expand the reader knowledge about the story universe. But the problem here is "slowly". Part of what is going on (and *why* is going on) is told very late in the story. +The biggest problem I found was that the story starts midway. Surely, this is +not something new, as other books take the same approach and then, slowly, +expand the reader knowledge about the story universe. But the problem here is +"slowly". Part of what is going on (and *why* is going on) is told very late +in the story. -Also, the end, although manages to capture your attention, is cliche at best. \ No newline at end of file +Also, the end, although manages to capture your attention, is cliche at best. diff --git a/content/reviews/books/the-end-of-all-things-old-mans-war-6.md b/content/reviews/books/the-end-of-all-things-old-mans-war-6.md index 8071a1d..d46404e 100644 --- a/content/reviews/books/the-end-of-all-things-old-mans-war-6.md +++ b/content/reviews/books/the-end-of-all-things-old-mans-war-6.md @@ -2,15 +2,29 @@ title = "The End of All Things (Old Man's War, #6) - John Scalzi" date = 2017-02-10 -category = "review" - [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "reviews", "scifi", "old man's war"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/23168809-the-end-of-all-things): +Humans expanded into space... only to find a universe populated with multiple +alien species bent on their destruction. Thus was the Colonial Union formed, +to help protect us from a hostile universe. The Colonial Union used the Earth +and its excess population for colonists and soldiers. It was a good +arrangement... for the Colonial Union. Then the Earth said: no more. + + + {{ stars(stars=4) }} -While all the other books in the series are more about "fight" and "tactics", this is way more political. +While all the other books in the series are more about "fight" and "tactics", +this is way more political. -After all the events in the series, the story finally reached a point where a cold war is present and the "action" is more about talk and creating pacts than exploding stuff. Which, to be honest, felt like the natural way the story should go. +After all the events in the series, the story finally reached a point where a +cold war is present and the "action" is more about talk and creating pacts +than exploding stuff. Which, to be honest, felt like the natural way the story +should go. -If you like the explosions and stuff, you may feel a bit down by this, but you have to give a change for the exploration of all other aspects of the universe created. \ No newline at end of file +If you like the explosions and stuff, you may feel a bit down by this, but you +have to give a change for the exploration of all other aspects of the universe +created. diff --git a/content/reviews/books/the-forever-war.md b/content/reviews/books/the-forever-war.md index dbd8b45..68bf21d 100644 --- a/content/reviews/books/the-forever-war.md +++ b/content/reviews/books/the-forever-war.md @@ -2,19 +2,46 @@ title = "The Forever War - Joe Haldeman" date = 2014-12-05 -category = "review" - [taxonomies] -tags = ["books", "en-au", "joe haldeman"] +tags = ["books", "joe haldeman", "reviews", "scifi", "the forever war"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/21611.The_Forever_War): +The Earth's leaders have drawn a line in the interstellar sand—despite the +fact that the fierce alien enemy that they would oppose is inscrutable, +unconquerable, and very far away. A reluctant conscript drafted into an elite +Military unit, Private William Mandella has been propelled through space and +time to fight in the distant thousand-year conflict; to perform his duties +without rancor and even rise up through military ranks. Pvt. Mandella is +willing to do whatever it takes to survive the ordeal and return home. But +"home" may be even more terrifying than battle, because, thanks to the time +dilation caused by space travel, Mandella is aging months while the Earth he +left behind is aging centuries. + + + {{ stars(stars=5) }} -After I finished this book I had to ask myself why I never read anything else by Haldeman. +After I finished this book I had to ask myself why I never read anything else +by Haldeman. -In a way, this book seems to be the counterpart of Heinlen's "Starship Troopers": While Heinlein shows how smart the army can be, Haldeman seems to show how the army can be pretty stupid sometimes. +In a way, this book seems to be the counterpart of Heinlen's "Starship +Troopers": While Heinlein shows how smart the army can be, Haldeman seems to +show how the army can be pretty stupid sometimes. -It follows the story of William Mandella, who gets in the very first war against an alien race that suddenly destroyed a colonizing ship. Due the way humanity uses to travel the unverse, what happens in just a few days/weeks to soldiers in-route, the everyone on Earth it takes years if not decades. So, in the end, although Mandella gets into only 3 battles, his time on the battlefield (well, on the way to the battlefield and back) goes around 900 years. +It follows the story of William Mandella, who gets in the very first war +against an alien race that suddenly destroyed a colonizing ship. Due the way +humanity uses to travel the unverse, what happens in just a few days/weeks to +soldiers in-route, the everyone on Earth it takes years if not decades. So, in +the end, although Mandella gets into only 3 battles, his time on the +battlefield (well, on the way to the battlefield and back) goes around 900 +years. -Also, there are some very clever things Haldeman did. At the very start, I thought the story was a bit sexist. It turns out it was a very well thought point Haldeman did to make a very long arc -- more like a criticism of the sexism in the 70s than some hidden agenda towards sexism. +Also, there are some very clever things Haldeman did. At the very start, I +thought the story was a bit sexist. It turns out it was a very well thought +point Haldeman did to make a very long arc -- more like a criticism of the +sexism in the 70s than some hidden agenda towards sexism. -If I didn't had just read yet another book about wars, I'd probably keep going through the series. But I guess I deserve a break after going through two different wars. \ No newline at end of file +If I didn't had just read yet another book about wars, I'd probably keep going +through the series. But I guess I deserve a break after going through two +different wars. diff --git a/content/reviews/books/the-ghost-brigades-old-mans-war-2.md b/content/reviews/books/the-ghost-brigades-old-mans-war-2.md index 49870ee..0774818 100644 --- a/content/reviews/books/the-ghost-brigades-old-mans-war-2.md +++ b/content/reviews/books/the-ghost-brigades-old-mans-war-2.md @@ -2,19 +2,41 @@ title = "The Ghost Brigades (Old Man's War, #2) - John Scalzi" date = 2016-04-21 -category = "review" - [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "reviews", "scifi", "old man's war"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/239399.The_Ghost_Brigades): +The Ghost Brigades are the Special Forces of the Colonial Defense Forces, +elite troops created from the DNA of the dead and turned into the perfect +soldiers for the CDF's toughest operations. They’re young, they’re fast and +strong, and they’re totally without normal human qualms. + +The universe is a dangerous place for humanity—and it's about to become far +more dangerous. Three races that humans have clashed with before have allied +to halt our expansion into space. Their linchpin: the turncoat military +scientist Charles Boutin, who knows the CDF’s biggest military secrets. To +prevail, the CDF must find out why Boutin did what he did. + + + {{ stars(stars=5) }} -Reading another "Old Man's War" after a long time since the very first is a weird experience. Mostly because you forgot half of the stuff, and the other half is buried somewhere in a fuzzy old memory. +Reading another "Old Man's War" after a long time since the very first is a +weird experience. Mostly because you forgot half of the stuff, and the other +half is buried somewhere in a fuzzy old memory. -And then the names appear in the story. And *then* you remember most of the stuff. +And then the names appear in the story. And *then* you remember most of the +stuff. -Thing is, this book does very little connection with the first one. While "_Old Man's War_" explored the life of a man in a new body in a very long battle, this book focuses on the other half of the book, Jane Sagan, the soldier built with the DNA of the man in the new body. +Thing is, this book does very little connection with the first one. While +"_Old Man's War_" explored the life of a man in a new body in a very long +battle, this book focuses on the other half of the book, Jane Sagan, the +soldier built with the DNA of the man in the new body. -So now we have the battles of Jane Sagan as a CDF soldier. But the book is really what *people* are: The bodies? Their personality? Their memories? +So now we have the battles of Jane Sagan as a CDF soldier. But the book is +really what *people* are: The bodies? Their personality? Their memories? -Unfortunately, it doesn't go as deep as it could in this topic but, on the other hand, the story is mostly solid, the writing is easy to read and the story itself have a good pacing. \ No newline at end of file +Unfortunately, it doesn't go as deep as it could in this topic but, on the +other hand, the story is mostly solid, the writing is easy to read and the +story itself have a good pacing. diff --git a/content/reviews/books/the-gunslinger-the-dark-tower-1.md b/content/reviews/books/the-gunslinger-the-dark-tower-1.md index 321547f..7cea43b 100644 --- a/content/reviews/books/the-gunslinger-the-dark-tower-1.md +++ b/content/reviews/books/the-gunslinger-the-dark-tower-1.md @@ -2,15 +2,30 @@ title = "The Gunslinger (The Dark Tower, #1) - Stephen King" date = 2017-06-11 -category = "review" - [taxonomies] -tags = ["books", "en-au", "stephen king"] +tags = ["books", "stephen king", "reviews", "the dark tower"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/43615.The_Gunslinger): +In the first book of this brilliant series, Stephen King introduces readers to +one of his most enigmatic heroes, Roland of Gilead, The Last Gunslinger. He is +a haunting figure, a loner on a spellbinding journey into good and evil. In +his desolate world, which frighteningly mirrors our own, Roland pursues The +Man in Black, encounters an alluring woman named Alice, and begins a +friendship with the Kid from Earth called Jake. Both grippingly realistic and +eerily dreamlike, The Gunslinger leaves readers eagerly awaiting the next +chapter. + + + {{ stars(stars=3) }} It pretty much felt like "the movie that started the series" from the 80s. -A lot of the stuff is basically the Gunslinger telling his story or thinking about the past. Sure it gives a nice explanation about the current status of the characters, but it also drains the amount of "current status". +A lot of the stuff is basically the Gunslinger telling his story or thinking +about the past. Sure it gives a nice explanation about the current status of +the characters, but it also drains the amount of "current status". -Also, some descriptions felt hard to follow. Sure it's easy to explain how a train station looks like and what's in it, but a cave... Good luck following what's happening there. \ No newline at end of file +Also, some descriptions felt hard to follow. Sure it's easy to explain how a +train station looks like and what's in it, but a cave... Good luck following +what's happening there. diff --git a/content/reviews/books/the-human-division-old-mans-war-5.md b/content/reviews/books/the-human-division-old-mans-war-5.md index cec467a..84aca1b 100644 --- a/content/reviews/books/the-human-division-old-mans-war-5.md +++ b/content/reviews/books/the-human-division-old-mans-war-5.md @@ -5,12 +5,26 @@ date = 2017-02-04 category = "review" [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "reviews", "old man's war", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/15698479-the-human-division): +Following the events of The Last Colony, John Scalzi tells the story of the +fight to maintain the unity of the human race. + + + {{ stars(stars=3) }} -In [book:Zoe's Tale|2102600], Scalzi mentions that he wanted to get away from John Perry and Jane, so the book is the same as The Last Colony, but from Zoe's point of view. +In "Zoe's Tale", Scalzi mentions that he wanted to get away from John Perry +and Jane, so the book is the same as The Last Colony, but from Zoe's point of +view. -This tendency keeps going on here, as it focus on Harry Wilson, one of John Perry mates in the first book -- and heck if I could remember that if the book haven't told me. +This tendency keeps going on here, as it focus on Harry Wilson, one of John +Perry mates in the first book -- and heck if I could remember that if the book +haven't told me. -The book is full of action, but its ending is kinda deceptive: It doesn't close the ties it opened, it just leaves a huge plot without explanation -- and one can assume it just something to bridge to the next book, [book:The End of All Things|23168809]. \ No newline at end of file +The book is full of action, but its ending is kinda deceptive: It doesn't +close the ties it opened, it just leaves a huge plot without explanation -- +and one can assume it just something to bridge to the next book, [book:The End +of All Things|23168809]. diff --git a/content/reviews/books/the-island-of-doctor-moreau-unabridged.md b/content/reviews/books/the-island-of-doctor-moreau-unabridged.md index 4958027..4a526b1 100644 --- a/content/reviews/books/the-island-of-doctor-moreau-unabridged.md +++ b/content/reviews/books/the-island-of-doctor-moreau-unabridged.md @@ -2,21 +2,45 @@ title = "The Island of Doctor Moreau (Unabridged) - H.G. Wells" date = 2014-12-09 -category = "review" - [taxonomies] -tags = ["books", "en-au", "h.g. wells"] +tags = ["books", "h.g. wells", "fantasy", "scifi", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/29981.The_Island_of_Doctor_Moreau): +While this riveting tale was intended to be a commentary on evolution, divine +creation, and the tension between human nature and culture, modern readers +familiar with genetic engineering will marvel at Wells’s prediction of the +ethical issues raised by producing “smarter” human beings or bringing back +extinct species. These levels of interpretation add a richness to Prendick’s +adventures on Dr. Moreau’s island of lost souls without distracting from what +is still a rip-roaring good read. + + + {{ stars(stars=4) }} -What brought me to "The Island of Doctor Moreau" was the movie with Marlon Brando. Yup, you read that right: It was the catastrophic (by IMDB comments) movie that made me read the book. +What brought me to "The Island of Doctor Moreau" was the movie with Marlon +Brando. Yup, you read that right: It was the catastrophic (by IMDB comments) +movie that made me read the book. -For all that I can remember, the movie goes to explore the fact that some people want to be Gods of others. It explores much of our egocentrism, how we find outselves better than anyone else and such (but my memory could be fading after all this time). +For all that I can remember, the movie goes to explore the fact that some +people want to be Gods of others. It explores much of our egocentrism, how we +find outselves better than anyone else and such (but my memory could be fading +after all this time). -The book, on the other hand, goes in a way more simpler and way more interesting concept: our intellect vs our instincts. +The book, on the other hand, goes in a way more simpler and way more +interesting concept: our intellect vs our instincts. -Moreau turns animals into anthropomorphic beings, including changes in the brain to allow them talk and understand most basic stuff. But something keeps bringing their instincts back, to the point that they lose their "humanity" and revert to... animals. From that point, from that basic premise, Wells explores what it is to be a human and what it is to be a beast. +Moreau turns animals into anthropomorphic beings, including changes in the +brain to allow them talk and understand most basic stuff. But something keeps +bringing their instincts back, to the point that they lose their "humanity" +and revert to... animals. From that point, from that basic premise, Wells +explores what it is to be a human and what it is to be a beast. -The best way to surmise the whole thing is this little gem in the very end of the book (hence why I marked *everything* a spoiler): +The best way to surmise the whole thing is this little gem in the very end of +the book: ->I, Moreau (by his passion for research), Montgomery (by his passion for drink), the Beast People with their instincts and mental restrictions, were torn and crushed, ruthlessly, inevitably, amid the infinite complexity of its incessant wheels. \ No newline at end of file +> I, Moreau (by his passion for research), Montgomery (by his passion for +> drink), the Beast People with their instincts and mental restrictions, were +> torn and crushed, ruthlessly, inevitably, amid the infinite complexity of +> its incessant wheels. diff --git a/content/reviews/books/the-last-colony-old-mans-war-3.md b/content/reviews/books/the-last-colony-old-mans-war-3.md index 6103792..8c56ff8 100644 --- a/content/reviews/books/the-last-colony-old-mans-war-3.md +++ b/content/reviews/books/the-last-colony-old-mans-war-3.md @@ -2,21 +2,44 @@ title = "The Last Colony (Old Man's War #3) - John Scalzi" date = 2016-04-23 -category = "review" - [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "scifi", "old man's war", "reviews"] +++ -{{ stars(stars=5) }} - -What would happen if genetic soldiers, after returning to their normal selves, had to fight a different fight? -John Perry and Jane Sagan, now being the parents of Zoë Boutin, have to manage and save a colony in a time when every other race in the universe decided to fight the human expansion. +[GoodReads Summary](https://www.goodreads.com/book/show/88071.The_Last_Colony): +Retired from his fighting days, John Perry is now village ombudsman for a +human colony on distant Huckleberry. With his wife, former Special Forces +warrior Jane Sagan, he farms several acres, adjudicates local disputes, and +enjoys watching his adopted daughter grow up. -In some ways, it felt like the boring parts of _Children of the Mind_, with annoying descriptions of a different planet, with its different fauna and flora and whatnot. I mean, for something more thoughtful, it gets boring pretty quick. + -Also, there is this weird "let me show how John is smart, because he has almost 100 years" thingy. Every time the colony gets into trouble, John comes with a solution. It's not Jane, the intelligence soldier that solves this, 'cause she's only 10 or so years old. Actually, Jane logistics is rarely brought into play, so she mostly sits on the background like a deus ex machina due her past. And John never gets into a corner he can't escape. - -Although these things are annoying, it doesn't bring the whole story to the ground: yup, the flora and fauna are boring, but they are a couple of pages; yup, Jane logistics is mostly through under the rug, but we have John; John never gets into a corner he can't escape or doesn't have a solution, either by intelligence or politics, but at least the story doesn't stall in those situations (well, because the situations don't exists, anyway). +{{ stars(stars=5) }} -As usual, a good, fast paced sci-fi book, like the others from Scalzi. \ No newline at end of file +What would happen if genetic soldiers, after returning to their normal selves, +had to fight a different fight? + +John Perry and Jane Sagan, now being the parents of Zoë Boutin, have to manage +and save a colony in a time when every other race in the universe decided to +fight the human expansion. + +In some ways, it felt like the boring parts of _Children of the Mind_, with +annoying descriptions of a different planet, with its different fauna and +flora and whatnot. I mean, for something more thoughtful, it gets boring +pretty quick. + +Also, there is this weird "let me show how John is smart, because he has +almost 100 years" thingy. Every time the colony gets into trouble, John comes +with a solution. It's not Jane, the intelligence soldier that solves this, +'cause she's only 10 or so years old. Actually, Jane logistics is rarely +brought into play, so she mostly sits on the background like a deus ex machina +due her past. And John never gets into a corner he can't escape. + +Although these things are annoying, it doesn't bring the whole story to the +ground: yup, the flora and fauna are boring, but they are a couple of pages; +yup, Jane logistics is mostly through under the rug, but we have John; John +never gets into a corner he can't escape or doesn't have a solution, either by +intelligence or politics, but at least the story doesn't stall in those +situations (well, because the situations don't exists, anyway). + +As usual, a good, fast paced sci-fi book, like the others from Scalzi. diff --git a/content/reviews/books/the-little-book-of-htmlcss-coding-guidelines.md b/content/reviews/books/the-little-book-of-htmlcss-coding-guidelines.md index bb5e753..572cebd 100644 --- a/content/reviews/books/the-little-book-of-htmlcss-coding-guidelines.md +++ b/content/reviews/books/the-little-book-of-htmlcss-coding-guidelines.md @@ -2,17 +2,31 @@ title = "The Little Book of HTML/CSS Coding Guidelines - Jens Oliver Meiert" date = 2016-10-18 -category = "review" - [taxonomies] -tags = ["books", "en-au", "jens oliver meiert"] +tags = ["books", "jens oliver meiert", "html", "css", "web development", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/28196387-the-little-book-of-html-css-coding-guidelines): +A proper plan can improve your code, including your HTML documents and CSS +style sheets. Jens Oliver Meiert explores the theory and practice of coding +guidelines and shows, using Google’s HTML and CSS standards as a particular +example, how consistency and care can make the code base you create today much +easier to deal with when you—or someone else—work on it later. + + + {{ stars(stars=3) }} There isn't much to say about this book, because this book doesn't say much. -Actually, you could say it says half of what it should, since half of the book is not about the guidelines, but about how great guidelines are. Not that useless, but a simply "they are good, Mkay?" would suffice. +Actually, you could say it says half of what it should, since half of the book +is not about the guidelines, but about how great guidelines are. Not that +useless, but a simply "they are good, Mkay?" would suffice. -About the guidelines themselves, they are heavily based on Google guidelines, mostly because those guidelines and this book have the same author. There is no amazing things or suggestions, mostly of them are guidelines that everybody follows and others are mostly harmless in the sense that they don't affect reading, like double quotes instead of single quotes. +About the guidelines themselves, they are heavily based on Google guidelines, +mostly because those guidelines and this book have the same author. There is +no amazing things or suggestions, mostly of them are guidelines that everybody +follows and others are mostly harmless in the sense that they don't affect +reading, like double quotes instead of single quotes. -So, nothing really ground breaking, but not bad either. \ No newline at end of file +So, nothing really ground breaking, but not bad either. diff --git a/content/reviews/books/the-martian.md b/content/reviews/books/the-martian.md index c8dec39..defa601 100644 --- a/content/reviews/books/the-martian.md +++ b/content/reviews/books/the-martian.md @@ -2,19 +2,35 @@ title = "The Martian - Andy Weir" date = 2015-07-18 -category = "review" - [taxonomies] -tags = ["books", "en-au", "andy weir"] +tags = ["books", "andy weir", "review", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18007564-the-martian): +Six days ago, astronaut Mark Watney became one of the first people to walk on +Mars. + +Now, he’s sure he’ll be the first person to die there. + + + {{ stars(stars=5) }} -Initial warning: I'm a science nerd. Not that I'm good at science, but I really enjoy reading about science: Tell me how to split an atom and I get a boner; show me a path around the space with two slingshots effect and I jizz in my pants. +Initial warning: I'm a science nerd. Not that I'm good at science, but I +really enjoy reading about science: Tell me how to split an atom and I get a +boner; show me a path around the space with two slingshots effect and I jizz +in my pants. -That's why I liked this book this much. It is kinda like the movie "The Core", but without the bullshit plot and materials and whatnot. +That's why I liked this book this much. It is kinda like the movie "The Core", +but without the bullshit plot and materials and whatnot. -So it seemed, at first, that the book was only about one guy lost in Mars and his attempts to survive. But the book encompasses a lot more than that. Without giving too much spoilers here, it explores a bit of science, how the space companies work, how much work it takes to launch a single rocket and so on. +So it seemed, at first, that the book was only about one guy lost in Mars and +his attempts to survive. But the book encompasses a lot more than that. +Without giving too much spoilers here, it explores a bit of science, how the +space companies work, how much work it takes to launch a single rocket and so +on. -As I mentioned, there is a *lot* of science in the book: How create water, how to create hydrogen, chemical reactions... +As I mentioned, there is a *lot* of science in the book: How create water, how +to create hydrogen, chemical reactions... -In the end, it is a really good book if you're a nerd. \ No newline at end of file +In the end, it is a really good book if you're a nerd. diff --git a/content/reviews/books/the-origin-of-names-words-and-everything-in-between.md b/content/reviews/books/the-origin-of-names-words-and-everything-in-between.md index f0b4ed0..08c8a8c 100644 --- a/content/reviews/books/the-origin-of-names-words-and-everything-in-between.md +++ b/content/reviews/books/the-origin-of-names-words-and-everything-in-between.md @@ -2,10 +2,8 @@ title = "The Origin of Names, Words and Everything in Between - Patrick Foote" date = 2018-11-30 -category = "reviews" - [taxonomies] -tags = ["books", "en-au", "etymology", "patrick foote"] +tags = ["books", "etymology", "patrick foote", "reviews"] +++ [GoodReads summary](https://www.goodreads.com/book/show/41224588-the-origin-of-names-words-and-everything-in-between): diff --git a/content/reviews/books/the-planets-photographs-from-the-archives-of-nasa.md b/content/reviews/books/the-planets-photographs-from-the-archives-of-nasa.md index f48605b..fd5705f 100644 --- a/content/reviews/books/the-planets-photographs-from-the-archives-of-nasa.md +++ b/content/reviews/books/the-planets-photographs-from-the-archives-of-nasa.md @@ -2,12 +2,22 @@ title = "The Planets: Photographs from the Archives of NASA - Nirmala Nataraj, Bill Nye, U.S. Goverment" date = 2018-11-25 -category = "review" - [taxonomies] -tags = ["books", "en-au", "nirmala nataraj", "bill nye"] +tags = ["books", "nirmala nataraj", "bill nye", "reviews", "photos", "pictures"] +++ +[GoodReads Summary](https://www.goodreads.com/book/show/33889690-the-planets): +This magnificent volume offers a rich visual tour of the planets in our solar +system. More than 200 breathtaking photographs from the archives of NASA are +paired with extended captions detailing the science behind some of our cosmic +neighborhood's most extraordinary phenomena. Images of newly discovered areas +of Jupiter, fiery volcanoes on Venus, and many more reveal the astronomical +marvels of space in engrossing detail. Anyone with an interest in science, +astronomy, and the mysteries of the universe will delight in this +awe-inspiring guide to the wonders of the solar system. + + + {{ stars(stars=5) }} If I said this book was only about pictures of the several rocks in our solar diff --git a/content/reviews/books/the-story-behind-the-extraordinary-history-behind-ordinary-objects.md b/content/reviews/books/the-story-behind-the-extraordinary-history-behind-ordinary-objects.md index 1ff1772..f072285 100644 --- a/content/reviews/books/the-story-behind-the-extraordinary-history-behind-ordinary-objects.md +++ b/content/reviews/books/the-story-behind-the-extraordinary-history-behind-ordinary-objects.md @@ -2,19 +2,23 @@ title = "The Story Behind: The Extraordinary History Behind Ordinary Objects - Emily Prokop" date = 2018-11-24 -category = "review" - [taxonomies] -tags = ["en-au", "books", "reviews", "emily prokop"] +tags = ["books", "reviews", "emily prokop"] +++ +[GoodReads Summary](https://www.goodreads.com/book/show/38813455-the-story-behind): +Learn the fascinating history and trivia you never knew about things we use +daily from the host of The Story Behind podcast. + + + {{ stars(stars=4) }} One of the books from the "Trivia Champion" Humble Bundle. And yes, it belongs to a "Trivia Champion" bundle. The whole book consists on small stories about random objects: The smiley face, -the revolver, the hydrant, the wipper, all consist in a small story behind it +the revolver, the hydrant, the wiper, all consist in a small story behind it or some anecdote, like a campus on war due a water gun. The stories are small and funny. diff --git a/content/reviews/books/the-swift-programming-language.md b/content/reviews/books/the-swift-programming-language.md index 8e7fd45..626fe7c 100644 --- a/content/reviews/books/the-swift-programming-language.md +++ b/content/reviews/books/the-swift-programming-language.md @@ -2,17 +2,31 @@ title = "The Swift Programming Language - Apple Inc." date = 2017-02-26 -category = "review" - [taxonomies] -tags = ["books", "en-au", "apple inc."] +tags = ["books", "apple inc.", "reviews", "swift", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/22394477-the-swift-programming-language): +Swift is a new programming language for creating iOS and OS X apps. Swift +builds on the best of C and Objective-C, without the constraints of C +compatibility. Swift adopts safe programming patterns and adds modern features +to make programming easier, more flexible, and more fun. Swift’s clean slate, +backed by the mature and much-loved Cocoa and Cocoa Touch frameworks, is an +opportunity to reimagine how software development works. + + + {{ stars(stars=5) }} -Let's skip the language itself for a moment and focus on the writing of the book. +Let's skip the language itself for a moment and focus on the writing of the +book. -The interesting bit is the first 20-or-so pages. It starts with a very simple, very succinct explanation of the language, so if you any programming language, you can just start writing Swift code picking the pointers in those pages. +The interesting bit is the first 20-or-so pages. It starts with a very simple, +very succinct explanation of the language, so if you any programming language, +you can just start writing Swift code picking the pointers in those pages. -Then, the real content starts: It goes very deep, explaining every point in great detail, with expanding examples that start very simple at the start of the chapter and then go increasingly going complex to explain each point. +Then, the real content starts: It goes very deep, explaining every point in +great detail, with expanding examples that start very simple at the start of +the chapter and then go increasingly going complex to explain each point. -Really interesting way to explain a language. \ No newline at end of file +Really interesting way to explain a language. diff --git a/content/reviews/books/the-waste-lands-the-dark-tower-3.md b/content/reviews/books/the-waste-lands-the-dark-tower-3.md index bf9e971..cc7b5d9 100644 --- a/content/reviews/books/the-waste-lands-the-dark-tower-3.md +++ b/content/reviews/books/the-waste-lands-the-dark-tower-3.md @@ -2,21 +2,43 @@ title = "The Waste Lands (The Dark Tower #3) - Stephen King" date = 2017-09-04 -category = "review" - [taxonomies] -tags = ["books", "en-au", "stephen king"] +tags = ["books", "stephen king", "the dark tower", "reviews", "the dark tower", "fiction"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/34084.The_Waste_Lands): +Several months have passed, and Roland’s two new tet-mates have become +proficient gunslingers. Eddie Dean has given up heroin, and Odetta’s two +selves have joined, becoming the stronger and more balanced personality of +Susannah Dean. But while battling The Pusher in 1977 New York, Roland altered +ka by saving the life of Jake Chambers, a boy who—in Roland’s where and +when—has already died. Now Roland and Jake exist in different worlds, but they +are joined by the same madness: the paradox of double memories. Roland, +Susannah, and Eddie must draw Jake into Mid-World then follow the Path of the +Beam all the way to the Dark Tower. But nothing is easy in Mid-World. Along +the way our tet stumbles into the ruined city of Lud, and are caught between +the warring gangs of the Pubes and the Grays. The only way out of Lud is to +wake Blaine the Mono, an insane train that has a passion for riddling, and for +suicidal journeys. + + + + {{ stars(stars=4) }} The very first book was mostly a backstory to the series. The second book was the first "in the story" of the series. -This, the third, is mostly King going "Well, now I'm writer, I can write whatever I can". And so he does. +This, the third, is mostly King going "Well, now I'm writer, I can write +whatever I can". And so he does. -The story flows nicely and a lot of things that you could feel King was holding back in the second story are not here. Whatever he things he can do, he does. So the story goes into larger arcs, deeper content and so on. +The story flows nicely and a lot of things that you could feel King was +holding back in the second story are not here. Whatever he things he can do, +he does. So the story goes into larger arcs, deeper content and so on. -The only downside is the ending. About 10% of book you feel like that "Oh shit, he's not going to defuse the bomb" or whatever happened in the old TV series and you can feel the "To be continued." coming. +The only downside is the ending. About 10% of book you feel like that "Oh +shit, he's not going to defuse the bomb" or whatever happened in the old TV +series and you can feel the "To be continued." coming. -And "To be continued" comes. \ No newline at end of file +And "To be continued" comes. diff --git a/content/reviews/books/the-where-the-why-the-how.md b/content/reviews/books/the-where-the-why-the-how.md index 10856c0..790dc14 100644 --- a/content/reviews/books/the-where-the-why-the-how.md +++ b/content/reviews/books/the-where-the-why-the-how.md @@ -2,10 +2,11 @@ title = "The Where, the Why, and the How: 75 Artists Illustrate Wondrous Mysteries of Science - Matt LaMothe, Julia Rothman, Jenny Volvovski, David Macaulay" date = 2019-02-17 -[taxomonies] -tags = ["books", "reviews", "en-au", "science", "illutations", "matt lamothe", "julia rothman", "jenny volvovski", "david macaulay"] +[taxonomies] +tags = ["books", "reviews", "science", "illutations", "matt lamothe", "julia rothman", "jenny volvovski", "david macaulay"] +++ +[GoodReads Summary](https://www.goodreads.com/book/show/14553766-the-where-the-why-and-the-how): A science book like no other, The Where, the Why, and the How turns loose 75 of today's hottest artists onto life's vast questions, from how we got here to where we are going. Inside these pages some of the biggest (and smallest) diff --git a/content/reviews/books/the-wolfs-hour.md b/content/reviews/books/the-wolfs-hour.md index add6a0e..ebe450b 100644 --- a/content/reviews/books/the-wolfs-hour.md +++ b/content/reviews/books/the-wolfs-hour.md @@ -3,9 +3,10 @@ title = "The Wolf's Hour - Robert R. McCammon" date = 2019-02-16 [taxonomies] -tags = ["books", "reviews", "en-au", "werewolves", "robert r mccammon"] +tags = ["books", "reviews", "werewolves", "robert r mccammon", "fantasy"] +++ +[GoodReads Summary](https://www.goodreads.com/book/show/11551.The_Wolf_s_Hour): Michael Gallatin is a British spy with a peculiar talent: the ability to transform himself into a wolf. Although his work in North Africa helped the Allies win the continent in the early days of World War II, he quit the service diff --git a/content/reviews/books/turing-e-o-computador-em-90-minutos.md b/content/reviews/books/turing-e-o-computador-em-90-minutos.md index aecc643..59a63a1 100644 --- a/content/reviews/books/turing-e-o-computador-em-90-minutos.md +++ b/content/reviews/books/turing-e-o-computador-em-90-minutos.md @@ -2,17 +2,38 @@ title = "Turing e o Computador em 90 minutos - Paul Strathern" date = 2017-02-19 -category = "review" - [taxonomies] -tags = ["books", "en-au", "paul strathern"] +tags = ["books", "pt-br", "paul strathern", "review", "alan turing", "história", "history"] +++ + +[Resumo GoodReads](https://www.goodreads.com/book/show/24921251-turing-e-o-computador-em-90-minutos): +Sem dúvida o computador é um dos maiores feitos do século XX. Mas quantos de +nós sabemos como ele funciona? E quantos conhecem Alan Turing, pioneiro no +desenvolvimento do computador e que ajudou a decifrar os códigos Enigma +durante a II Guerra? Esse livro é um delicioso instantâneo de Turing e dos +progressos da computação. + + + {{ stars(stars=3) }} (Em 90 minutos ou um pouco mais, no meu caso). -Turing sempre foi uma figura representativa na informática: sabe-se que boa parte das suas conjecturas são o que tornaram os computadores o que são (a boa definição de "máquina de Turing") e seus questionamentos continuam sendo questinamentos válidos (ainda o "teste de Turing"). E conhece-se que seu trabalho na sua máquina acabou resolvendo o problema de decifrar o Enigma, a máquina criptográfica utilizada pelos nazistas. E sabe-se que foi preso e sofreu castração química por ser homossexual. +Turing sempre foi uma figura representativa na informática: sabe-se que boa +parte das suas conjecturas são o que tornaram os computadores o que são (a boa +definição de "máquina de Turing") e seus questionamentos continuam sendo +questinamentos válidos (ainda o "teste de Turing"). E conhece-se que seu +trabalho na sua máquina acabou resolvendo o problema de decifrar o Enigma, a +máquina criptográfica utilizada pelos nazistas. E sabe-se que foi preso e +sofreu castração química por ser homossexual. Isso tudo pode ser visto, inclusive, no cinema. -Mas nem a apresentação feita nas faculdades nem o filme mostram exatamente o que estava acontencendo: Os avanços da época por Pascal, Schickard, Leibniz, Jacquard, Babbage e Boole; a construção do MADAM -- cuja existência nunca é contada por causa do ENIAC; a aparência de Turing (cuja descrição deixa a entender que sua foto clássica de cabelos cortados e barba feita era uma anomalia); seu comportamento promíscuo, em que saída a noite para procura de novos jovens homossexuais... Essas partes são contadas no livro em questão, que é um resumo do livro escrito por Andrew Hodges. \ No newline at end of file +Mas nem a apresentação feita nas faculdades nem o filme mostram exatamente o +que estava acontencendo: Os avanços da época por Pascal, Schickard, Leibniz, +Jacquard, Babbage e Boole; a construção do MADAM -- cuja existência nunca é +contada por causa do ENIAC; a aparência de Turing (cuja descrição deixa a +entender que sua foto clássica de cabelos cortados e barba feita era uma +anomalia); seu comportamento promíscuo, em que saída a noite para procura de +novos jovens homossexuais... Essas partes são contadas no livro em questão, +que é um resumo do livro escrito por Andrew Hodges. diff --git a/content/reviews/books/typescript-succinctly.md b/content/reviews/books/typescript-succinctly.md index 9a1902f..47d8e9a 100644 --- a/content/reviews/books/typescript-succinctly.md +++ b/content/reviews/books/typescript-succinctly.md @@ -2,13 +2,29 @@ title = "TypeScript Succinctly - Steve Fenton" date = 2016-02-22 -category = "review" - [taxonomies] -tags = ["books", "en-au", "steve fenton"] +tags = ["books", "steve fenton", "javascript", "typescript", "web development", "reviews", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/18405331-typescript-succinctly): +The extensive adoption of JavaScript for application development, and the +ability to use HTML and JavaScript to create Windows Store apps, has made +JavaScript a vital part of the Windows development ecosystem. Microsoft has +done extensive work to make JavaScript easier to use. Microsoft's TypeScript +extends many familiar features of .NET programming to JavaScript. With +TypeScript Succinctly by Steve Fenton, you will learn how TypeScript provides +optional static typing and classes to JavaScript development, how to create +and load modules, and how to work with existing JavaScript libraries through +ambient declarations. TypeScript is even significantly integrated with Visual +Studio to provide the autocompletion and type checking you are most +comfortable with. + + + {{ stars(stars=4) }} -Without jumping into too much detail, the book gives a little introduction to TypeScript, without the whole bullshit other books like to add. So it is that I probably highlighted the whole thing. +Without jumping into too much detail, the book gives a little introduction to +TypeScript, without the whole bullshit other books like to add. So it is that +I probably highlighted the whole thing. -Don't expect to go deep into TypeScript and all its nuances, though. \ No newline at end of file +Don't expect to go deep into TypeScript and all its nuances, though. diff --git a/content/reviews/books/web-development-with-clojure-build-bulletproof-web-apps-with-less-code.md b/content/reviews/books/web-development-with-clojure-build-bulletproof-web-apps-with-less-code.md index fae0494..f98a50e 100644 --- a/content/reviews/books/web-development-with-clojure-build-bulletproof-web-apps-with-less-code.md +++ b/content/reviews/books/web-development-with-clojure-build-bulletproof-web-apps-with-less-code.md @@ -2,21 +2,48 @@ title = "Web Development with Clojure: Build Bulletproof Web Apps with Less Code - Dmitri Sotnikov" date = 2017-06-22 -category = "review" - [taxonomies] -tags = ["books", "en-au", "dmitri sotnikov"] +tags = ["books", "dmitri sotnikov", "reviews", "clojure", "web development", "it"] +++ -{{ stars(stars=2) }} - -First of all, this book suffers from the same mistakes every single Lisp-like language book I've read: They throw a truck at you, then slowly, while you're being crushed by it, explain each part that creates a truck -- In other words, they throw a large piece of code at you and then slowly explain each part of it. -Even worst, in the last parts, it's basically "here is truck, take it" -- very little explanation about the code itself, just "we'll do this" and code. What the pieces of code mean, that's entirely to you. +[GoodReads Summary](https://www.goodreads.com/book/show/18399028-web-development-with-clojure): +Modern web development needs modern tools. Web Development With Clojure shows +you how to apply Clojure programming fundamentals to build real-world +solutions. You'll develop all the pieces of a full web application in this +powerful language. If you already have some familiarity with Clojure, you'll +learn how to put it to serious practical use. If you're new to the language, +the book provides just enough Clojure to get down to business. -Another problem: no tests. The author prefers the REPL approach, which is okay for little projects, but for projects that should last longer than a weekend project. No only that, but even the tests are wrong, because it mocks the database -- Database is part of your project so it **should** be tested along all the other tests. + -And, on top of that, there is a REST server with sessions, and a lot of code just to keep the frontend session in sync with the server session. That's actually **not** how a REST server works. - -And while I usually don't comment the technology behind the book (because it's not the author's creation), I really have to ask if Clojure is the right tool for web servers. I mean, a lot about Clojure is about immutability and a lot about the shown code is forcing mutability -- one function even is composed with nothing but functions that force mutability. +{{ stars(stars=2) }} -So, not only the book itself doesn't give a clear picture about web development in Clojure, the language itself doesn't appear appropriate for such task. \ No newline at end of file +First of all, this book suffers from the same mistakes every single Lisp-like +language book I've read: They throw a truck at you, then slowly, while you're +being crushed by it, explain each part that creates a truck -- In other words, +they throw a large piece of code at you and then slowly explain each part of +it. + +Even worst, in the last parts, it's basically "here is truck, take it" -- very +little explanation about the code itself, just "we'll do this" and code. What +the pieces of code mean, that's entirely to you. + +Another problem: no tests. The author prefers the REPL approach, which is okay +for little projects, but for projects that should last longer than a weekend +project. No only that, but even the tests are wrong, because it mocks the +database -- Database is part of your project so it **should** be tested along +all the other tests. + +And, on top of that, there is a REST server with sessions, and a lot of code +just to keep the frontend session in sync with the server session. That's +actually **not** how a REST server works. + +And while I usually don't comment the technology behind the book (because it's +not the author's creation), I really have to ask if Clojure is the right tool +for web servers. I mean, a lot about Clojure is about immutability and a lot +about the shown code is forcing mutability -- one function even is composed +with nothing but functions that force mutability. + +So, not only the book itself doesn't give a clear picture about web +development in Clojure, the language itself doesn't appear appropriate for +such task. diff --git a/content/reviews/books/web-development-with-django-cookbook.md b/content/reviews/books/web-development-with-django-cookbook.md index 36aaf6b..e1f2476 100644 --- a/content/reviews/books/web-development-with-django-cookbook.md +++ b/content/reviews/books/web-development-with-django-cookbook.md @@ -2,19 +2,47 @@ title = "Web Development with Django Cookbook - Aidas Bendoraitis" date = 2016-07-10 -category = "review" - [taxonomies] -tags = ["books", "en-au", "aidas bendoraitis"] +tags = ["books", "aidas bendoraitis", "reviews", "python", "django", "web development", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/23477190-web-development-with-django-cookbook): +Over 70 practical recipes to create multilingual, responsive, and scalable +websites with Django About This Book Improve your skills by developing models, +forms, views, and templates Create a rich user experience using Ajax and other +JavaScript techniques A practical guide to writing and using APIs to import or +export data Who This Book Is For. + + + {{ stars(stars=1) }} -First point: This book is terribly outdated. It focus on Django 1.6, which is at least 3 versions behind the current one (at the time of this review). 1.6 is so old that you can't find its documentation on the Django Project page anymore. +First point: This book is terribly outdated. It focus on Django 1.6, which is +at least 3 versions behind the current one (at the time of this review). 1.6 +is so old that you can't find its documentation on the Django Project page +anymore. -Second point: This book is terrible. I mean, one of the very first examples it talks about a mixin with creation date and modified date, which is pretty damn easy with Django, but instead of using "auto_now=True" and/or "auto_now_add=True", it overrides save() on the model. Now terrible enough? Later in the book, it creates a templatetag to access model directly, which completely obliterates the MVT (model-view-template) model of Django. Still not terrible enough? Again in the very first part of the book, to prevent browser caching issues, it gives a recipe for using the SVN revision in the static path; the wrong part of it is: a) it means you'll have to have SVN in your server instead of using proper setup.py to deliver your apps, b) it does a system() call, which is slow, c) there is a prop in SVN which allows you to use "$Id$" to automatically save the revision on commit (pretty much like CSV) and d) If you're having caching issues, that's a problem with your webserver, not Django. +Second point: This book is terrible. I mean, one of the very first examples it +talks about a mixin with creation date and modified date, which is pretty damn +easy with Django, but instead of using "auto_now=True" and/or +"auto_now_add=True", it overrides save() on the model. Now terrible enough? +Later in the book, it creates a templatetag to access model directly, which +completely obliterates the MVT (model-view-template) model of Django. Still +not terrible enough? Again in the very first part of the book, to prevent +browser caching issues, it gives a recipe for using the SVN revision in the +static path; the wrong part of it is: a) it means you'll have to have SVN in +your server instead of using proper setup.py to deliver your apps, b) it does +a system() call, which is slow, c) there is a prop in SVN which allows you to +use "$Id$" to automatically save the revision on commit (pretty much like CSV) +and d) If you're having caching issues, that's a problem with your webserver, +not Django. -(I won't even talk about long chapters talking about MPTT with examples either don't show the tool properly or MPTT is so useless one could replace it with a single ForeignKey.) +(I won't even talk about long chapters talking about MPTT with examples either +don't show the tool properly or MPTT is so useless one could replace it with a +single ForeignKey.) -The whole book feels like someone searched for "django" on StackOverflow and dropped the first answers. +The whole book feels like someone searched for "django" on StackOverflow and +dropped the first answers. -In the end, the book is only good for giving you some ideas of what is available with Django, not how to properly develop a Django app. \ No newline at end of file +In the end, the book is only good for giving you some ideas of what is +available with Django, not how to properly develop a Django app. diff --git a/content/reviews/books/wikileaks-inside-julian-assanges-war-on-secrecy.md b/content/reviews/books/wikileaks-inside-julian-assanges-war-on-secrecy.md index 2b469df..94c1655 100644 --- a/content/reviews/books/wikileaks-inside-julian-assanges-war-on-secrecy.md +++ b/content/reviews/books/wikileaks-inside-julian-assanges-war-on-secrecy.md @@ -2,21 +2,44 @@ title = "WikiLeaks: Inside Julian Assange's War on Secrecy - David Leigh" date = 2015-03-29 -category = "review" - [taxonomies] -tags = ["books", "en-au", "david leigh"] +tags = ["books", "david leigh", "reviews", "history", "biography", "julian assange", "wikileaks"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/10318540-wikileaks): +A team of journalists with unparalleled inside access provides the first full, +in-depth account of WikiLeaks, its founder Julian Assange, and the ethical, +legal, and political controversies it has both uncovered and provoked. + + + {{ stars(stars=3) }} **Almost a Cablegate novelization** -The first comment I did on my updates about this book is "Words, words, words. This doesn't look good." This is my warning that there are some things the writer did that are completely unnecessary and could be thrown out without losing any context. There are a lot more of those "words, words, words" moments all over the content, so much that the book feels more like a novelization of the Cablegate events than a proper recounting of the events. +The first comment I did on my updates about this book is "Words, words, words. +This doesn't look good." This is my warning that there are some things the +writer did that are completely unnecessary and could be thrown out without +losing any context. There are a lot more of those "words, words, words" +moments all over the content, so much that the book feels more like a +novelization of the Cablegate events than a proper recounting of the events. It doesn't make the story itself bad, it is a good story with a lot of cruft. -But the story itself it's about Wikileaks, from its inception to the release of the so called Cablegate -- the release of several diplomatic cables. Actually, Wikileaks is just the background story here; the whole action is more about how The Guardian dealt with Assange and the other publishing partners than Wikileaks itself. - -It's not a bad story, even with the abundance of words. There are a lot of forgotten elements -- like the story behind Manning and his leaking -- which tend to be completely ignored at this point. But, again, there are too many unnecessary words that go nowhere. Prepare to get annoyed about the continuous mention of the some cable over and over again -- and see the said cable in its complete form in the end. - -(Why I'm mentioning this? 'Cause the book makes a huge deal of how several cables affected international politics, but keep mentioning the same three cables over and over again. I mean, if several where that important, why are the same three mentioned so many times?) \ No newline at end of file +But the story itself it's about Wikileaks, from its inception to the release +of the so called Cablegate -- the release of several diplomatic cables. +Actually, Wikileaks is just the background story here; the whole action is +more about how The Guardian dealt with Assange and the other publishing +partners than Wikileaks itself. + +It's not a bad story, even with the abundance of words. There are a lot of +forgotten elements -- like the story behind Manning and his leaking -- which +tend to be completely ignored at this point. But, again, there are too many +unnecessary words that go nowhere. Prepare to get annoyed about the continuous +mention of the some cable over and over again -- and see the said cable in its +complete form in the end. + +(Why I'm mentioning this? 'Cause the book makes a huge deal of how several +cables affected international politics, but keep mentioning the same three +cables over and over again. I mean, if several where that important, why are +the same three mentioned so many times?) diff --git a/content/reviews/books/will-eisners-the-spirit-who-killed-the-spirit.md b/content/reviews/books/will-eisners-the-spirit-who-killed-the-spirit.md index 502006c..7c510cc 100644 --- a/content/reviews/books/will-eisners-the-spirit-who-killed-the-spirit.md +++ b/content/reviews/books/will-eisners-the-spirit-who-killed-the-spirit.md @@ -2,19 +2,26 @@ title = "Will Eisner's the Spirit: Who Killed the Spirit? - Matt Wagner" date = 2017-09-04 -category = "review" - [taxonomies] -tags = ["books", "en-au", "matt wagner"] +tags = ["books", "matt wagner", "comics", "reviews"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/31170820-will-eisner-s-the-spirit): +To celebrate the 75th anniversary of Will Eisner's most iconic character, +Dynamite Entertainment proudly assembled the creative dream team of Eisner +Award-winning author Matt Wagner, artist Dan Schkade, and colorist Brennan +Wagner to honor the legend with an all-new adventure! + {{ stars(stars=2) }} In my teens, I got two Spirit books on a sale. -I absolutely loved the story and the lines. It was my first experience with adult comics: Color only when really needed, deep story without a good vs evil (well, it was, but it was not all black and white), excellent drawing... +I absolutely loved the story and the lines. It was my first experience with +adult comics: Color only when really needed, deep story without a good vs evil +(well, it was, but it was not all black and white), excellent drawing... This is not it. This is nothing like the original Spirit. -This is a sad rip off. \ No newline at end of file +This is a sad rip off. diff --git a/content/reviews/books/write-great-code-volume-i-understanding-the-machine.md b/content/reviews/books/write-great-code-volume-i-understanding-the-machine.md index 75e482e..7549238 100644 --- a/content/reviews/books/write-great-code-volume-i-understanding-the-machine.md +++ b/content/reviews/books/write-great-code-volume-i-understanding-the-machine.md @@ -5,16 +5,46 @@ date = 2016-10-05 category = "review" [taxonomies] -tags = ["books", "en-au", "randall hyde"] +tags = ["books", "randall hyde", "reviews", "coding", "computer architecture", "it"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/35873018-write-great-code): +Write Great Code, Volume 1 teaches machine organization, including numeric +representation; binary arithmetic and bit operations; floating point +representation; system and memory organization; character representation; +constants and types; digital design; CPU, instruction set, and memory +architecture; input and output; and how compilers work. + + + {{ stars(stars=1) }} -"Great code" is machine dependent and written in assembly. Or, at least, that's what this book makes you believe till the very last chapter, when it starts backtracking about writing code directly into CPU code. +"Great code" is machine dependent and written in assembly. Or, at least, +that's what this book makes you believe till the very last chapter, when it +starts backtracking about writing code directly into CPU code. -Now, don't get me wrong, it's not a terrible book -- it's a damn complete book about *computer architecture*, even being so out-of-date that there is no word about SSDs (when talking about storage), no mention about MP3s (when discussing about audio hardware), the top CPU discussed is Pentium, there is no word about UTF-8 (and mentions ASCII is used all around) and recommending search things on AltaVista. +Now, don't get me wrong, it's not a terrible book -- it's a damn complete book +about *computer architecture*, even being so out-of-date that there is no word +about SSDs (when talking about storage), no mention about MP3s (when +discussing about audio hardware), the top CPU discussed is Pentium, there is +no word about UTF-8 (and mentions ASCII is used all around) and recommending +search things on AltaVista. -The problem is discussing all this when the topic is "great code": Great code is not machine dependent; great code is not highly optimized code that runs extremely fast and uses very little memory; there are trade offs that you have to take in account when coding: Sure, you don't write something that uses all the available memory, but you write in a language that allows you to easily extend the code later and which your code reads exactly what you meant it to say. That's great code, not code that uses some multimedia extensions that is available since a very specific generation of CPUs. +The problem is discussing all this when the topic is "great code": Great code +is not machine dependent; great code is not highly optimized code that runs +extremely fast and uses very little memory; there are trade offs that you have +to take in account when coding: Sure, you don't write something that uses all +the available memory, but you write in a language that allows you to easily +extend the code later and which your code reads exactly what you meant it to +say. That's great code, not code that uses some multimedia extensions that is +available since a very specific generation of CPUs. -The book also goes into great lengths to explain stuff that is hardly useful. For example, there is a whole implementation of the floating point standard (IEEE 754), which is not optimized -- so, no great code -- and that's absolutely unnecessary, since this is done directly into the CPU (and, if it isn't, you have libraries ready for that). +The book also goes into great lengths to explain stuff that is hardly useful. +For example, there is a whole implementation of the floating point standard +(IEEE 754), which is not optimized -- so, no great code -- and that's +absolutely unnecessary, since this is done directly into the CPU (and, if it +isn't, you have libraries ready for that). -It could be that the "Great Code" will come in the later volumes, but ignoring what *is* great code (I mean, *real* great code) and just building a base for later is plainly greedy. \ No newline at end of file +It could be that the "Great Code" will come in the later volumes, but ignoring +what *is* great code (I mean, *real* great code) and just building a base for +later is plainly greedy. diff --git a/content/reviews/books/zoes-tale-old-mans-war-4.md b/content/reviews/books/zoes-tale-old-mans-war-4.md index ffff0a9..5fba21e 100644 --- a/content/reviews/books/zoes-tale-old-mans-war-4.md +++ b/content/reviews/books/zoes-tale-old-mans-war-4.md @@ -2,15 +2,36 @@ title = "Zoe's Tale (Old Man's War, #4) - John Scalzi" date = 2017-01-25 -category = "review" - [taxonomies] -tags = ["books", "en-au", "john scalzi"] +tags = ["books", "john scalzi", "reviews", "old man's war", "scifi"] +++ + +[GoodReads Summary](https://www.goodreads.com/book/show/2102600.Zoe_s_Tale): +Everyone on Earth knows the tale I am part of. But you don't know my tale: How +I did what I did — how I did what I had to do — not just to stay alive but to +keep you alive, too. All of you. I'm going to tell it to you now, the only way +I know how: not straight but true, the whole thing, to try make you feel what +I felt: the joy and terror and uncertainty, panic and wonder, despair and +hope. Everything that happened, bringing us to Earth, and Earth out of its +captivity. All through my eyes. + + + {{ stars(stars=4) }} -It's been awhile since I've read _The Last Colony_ and, when I started reading this book, I thought "I've already read this, but since I don't remember everything, no damage in reading it again". And somethings were different, so I thought "Well, my memory is not the same anymore, it seems." And when I finally finished the book and read the author's commentary about it, I finally realized I didn't read "Zoe's Tale". At all. +It's been awhile since I've read _The Last Colony_ and, when I started reading +this book, I thought "I've already read this, but since I don't remember +everything, no damage in reading it again". And somethings were different, so +I thought "Well, my memory is not the same anymore, it seems." And when I +finally finished the book and read the author's commentary about it, I finally +realized I didn't read "Zoe's Tale". At all. -Instead of going forward with the tale of Old Man's War main protagonists, Scalzi starts at the very start of "Last Colony" and tells the same story by the eyes of another character, this time (wanna guess?) Zoe. Kinda like [book:Shadow of the Giant|8647 (and its series), which follows Bean instead of Ender. +Instead of going forward with the tale of Old Man's War main protagonists, +Scalzi starts at the very start of "Last Colony" and tells the same story by +the eyes of another character, this time (wanna guess?) Zoe. Kinda like +[book:Shadow of the Giant|8647 (and its series), which follows Bean instead of +Ender. -It's a fun book -- I still love the way Scalzi writes -- but if you try to read after reading Last Colony, you may think you're reading the same thing again. \ No newline at end of file +It's a fun book -- I still love the way Scalzi writes -- but if you try to +read after reading Last Colony, you may think you're reading the same thing +again. diff --git a/content/thoughts/one-week-with-tiler/index.md b/content/thoughts/one-week-with-tiler/index.md index 6070b13..8de8159 100644 --- a/content/thoughts/one-week-with-tiler/index.md +++ b/content/thoughts/one-week-with-tiler/index.md @@ -3,7 +3,7 @@ title = "One Week with Tiler" date = 2019-01-19 [taxonomies] -tags = ["vim", "en-au", "plugins", "tiler", "tiling"] +tags = ["vim", "plugins", "tiler", "tiling"] +++ Tiler is a tiling split manager for VIM. Here is my experience with it diff --git a/content/thoughts/pre-order-the-case-of-no-mans-sky.md b/content/thoughts/pre-order-the-case-of-no-mans-sky.md index bededc6..ff0ac42 100644 --- a/content/thoughts/pre-order-the-case-of-no-mans-sky.md +++ b/content/thoughts/pre-order-the-case-of-no-mans-sky.md @@ -1,10 +1,9 @@ +++ title = "Pre-Orders: The Case of No Man's Sky" date = 2016-08-25 -category = "thoughts" [taxonomies] -tags = ["pre-order", "grim dawn", "no man's sky", "en-au"] +tags = ["pre-order", "grim dawn", "no man's sky"] +++ [No Man's Sky](http://www.no-mans-sky.com/) is getting a lot of heat recently diff --git a/content/thoughts/the-sad-life-of-walter-mitty.md b/content/thoughts/the-sad-life-of-walter-mitty.md index 11b9529..dca5677 100644 --- a/content/thoughts/the-sad-life-of-walter-mitty.md +++ b/content/thoughts/the-sad-life-of-walter-mitty.md @@ -1,10 +1,9 @@ +++ title = "The Sad Life of Walter Mitty" date = 2015-03-28 -category = "thoughts" [taxonomies] -tags = ["movies", "the secret life of walter mitty", "rethink", "review", "en-au"] +tags = ["movies", "the secret life of walter mitty", "rethink", "review"] +++ I once wrote about [The Secret Life of Walter diff --git a/content/thoughts/things-i-learnt-the-hard-way-the-book.md b/content/thoughts/things-i-learnt-the-hard-way-the-book.md index 3cb4a30..6ff96ca 100644 --- a/content/thoughts/things-i-learnt-the-hard-way-the-book.md +++ b/content/thoughts/things-i-learnt-the-hard-way-the-book.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way - The... Book?" date = 2019-06-14 [taxonomies] -tags = ["en-au", "programming", "work"] +tags = ["programming", "work"] +++ Random thought about the previous post about "Things I Learnt The Hard Way". diff --git a/content/thoughts/things-i-learnt-the-hard-way.md b/content/thoughts/things-i-learnt-the-hard-way.md index fbc8c2a..b5ae738 100644 --- a/content/thoughts/things-i-learnt-the-hard-way.md +++ b/content/thoughts/things-i-learnt-the-hard-way.md @@ -3,7 +3,7 @@ title = "Things I Learnt The Hard Way (in 30 Years of Software Development)" date = 2019-06-10 [taxonomies] -tags = ["en-au", "programming", "work"] +tags = ["programming", "work"] +++ This is a cynical, clinical collection of things I learnt in 30 years working