It's even more useless than the "4-hour work week". Tim is a cool guy, but the book looks like his diary with all the recipes that he has been meticiously testing on himself without any scientific or medical proof whatsoever.
Don't waste your time on it, just read a few of his blog posts.
My score is 2/5
The author considers his book as an introductional tutorial, which it's definitely not.
I was a bit disappointed first as it goes into too much detail on the basics of web development and Rub y the language, but then I got enlightened. This book is called "Introduction to Web Development with Ruby on Rails", therefore it doesn't expect its reader to have any experience with RoR, Ruby or web dev whatsoever.
I wish I had read a book like this before. Unfortunately, the heyday of RoR has been long gone, but this doesn't make this book any worse.
This book is a must read if you're thinking to touch any RoR project.
The most valuable asset that this book gives is its reading list given at the very end of it.
Tim Ferriss is a cool guy with a long list of achievements, I just don't agree with some of the things written in this book. Plus, as it was written in 2007 a lot of stuff that he tries to explain in detail like the easiness of creating your own info products and remote work ubiquity are considered as trivial and don't need a lengthy multi chapter explanation as, I assume, was the case in 2007.
The "low information diet" principle coined by Ferriss will take a place at the top of my own list of the things that I strive to do for self improvement.
Хорошо что я не прочитал эту книгу ранее когда ездил каждое утро по маршруту Москва-Петушки, достаточно тяжело ассоциироовать себя с героями и происшествиями этой книге.
По моему мнению эта книга это квинтэссенция повести о российской интеллигенции: маргинализированная, никому не нужная, ждущая когда же откроется магазин чтобы купить херес который поможет приблизиться к сути бытия и чтобы не так тянуло блевать.
Да, это герой уровня Гоголя и Пелевина. В каждом времени есть свои герои, но Венечка для меня навсегда останется примером того что ждет каждого беспомощного российского интеллигента нашедшего спасения от обыденных проблем в пьянстве: Сфинкс и нож в горле.
This book doesn't reinvent the wheel, it will not teach you anything new that you haven't heard of before. This is simply a cookbook of recipes on how to always stay relevant and drift with the flow in the right direction.
Very motivating, if you're a fan of Lifehacker that's definitely the book you need to read instantly.
Go in Practice is a nice small book that in my opinion should be the starting point for every Golang programmer. As the language is so small you can learn it in a few days, but its libraries are its biggest value if you ask me and this book tries to explain why those libraries have allowed to scaffold such projects as Docker and Kubernetes.
The book is boring sometimes, it goes in too much detail without a particular need. Explaining the methods of this or that class is too much of a burden for the readers in my opinion.
The biggest flaw of the book is also its biggest virtue. Even though I had no problems with running some of the code that's embedded in the book ( the version of the book in Safari is awful BTW) as the book promises to be a practical guide some the solutions to the problems the the author thinks one can face are a bit outdated. If you claim to give practical solutions than you need to update your book with the best solution that's currently available
VueJS is the new kid on the block, though it might look familiar to most of frontend developers who had experience with Angular 1.x prior to that. And that's not an coincedence due to that VueJS author was one of the former core contributors to Angular therefore he claims that he took the features that we of the most importance to community and got rid of the unneccessary complexity that Angular 2.x presents as its features.
Ok, let's go back to the book. The book is great, I can't say more about it. It reminds me of the Head First book series that was iconic to the IT newcomers back in the mid 2010's. Olga reminds Kathy Sierra a lot as they have a similar narratory style though Kathy usually gets in too much details as she expects her readers to have zero knowledge and Olga sometimes skips some of the concepts and gives a referrence to the book's complementary source code. It's hard to find it therefore I've made a fork that's will be more accessible for anyone https://github.com/mkoltsov/Vue.js-2-and-Bootstrap-4-Web-Development
The book gives a lot of practical examples on how to start writing actual webapps with Vue, it even goes to such extent as how to deploy it and manage its data.
I always thought of myself as of a quick learner, therefore I prefer to practice and hone my skill rather than reading long and lenghty books.
Unfortunately, that’s not the case with Go. I’ll give a try to “Go in Practice” from the same publisher in a hope that it will not leave me with lots of unanswered questions as this book did.
This book gave me a good momentum to start using some of the Ruby features I (i.e. Fibers ) that I was completely unaware before, though the amount of input it provides is not overwhelming which helps you to digest this book over a weekend.
That’s a good starter for anyone willing to start coding in Ruby 2.1, lots of examples are outdated if you aim for Ruby 2.4+
This is actually the first book about Python I’ve read even though I’ve used it extensively throughout the years.
My perception that this book proves is that Pythonistas are usually not programmers by trade, they’d come to programming either due to a lucky coincidence or by taking a wrong turn on the road of career hopping.
This book has promised to give a broad look on the Python’s ecosystem, it actually delivers on what it promises. But this look is so shallow that I can’t recommend this book for those who’s willing to get a deep dive into Python on a weekend. The technical details it gives look like author’s waving the hands in the air with no actual proof that I’m used to in Scala and Java books.
Good book, but I can’t recommend it to any professional programmer who’s used to technical/programming/mathematical books.
This book is considered a cornerstone of the DevOps movement. In my opinion, it might be that in the very beginning, but currently most of the concepts that it presents are obvious and outdated.
I will recommend it to be read to someone who’s new in the DevOps community, but if you’ve got a few years of experience in the area under your belt I would not.
It’s nice to have all good concepts under one cover, but reading a 400-pages long book that will tell you the history of GIT and SVN is pointless in my opinion. Most of the ideas presented in the book could be wrapped in one long yet succinct blog post.
This book actually reminds me of the book “Release it ” but with much less emphasis on actual technical patterns but with a stronger accent on soft skills.
It’s also complimentary to the “Phoenix Project” written by the same authors.
If you’ve skipped the “Phoenix Project” or you don’t like to read the novels, like I do, I would recommend you to start with this book as it has much more momentum than the first book.
It has a bunch of great inspiring examples of successes from the companies that have embarked on the “DevOps journey” which to me is the best part of this book. Also the book is relatively recent therefore a lot of its advices are quite innovative and might be even disturbing to some.
Sometimes I’m late for some of the most important events in my life. Hopefully, health is not the issue that I’ve missed. Self-awareness and consciousness have always been a nice thing to have under your belt.
This book helps to improve those skills by giving you a nice reference for all the good things you need to be aware of that might either help you to advance or suffer as a human being.
This book is nothing more than a composition of blog posts, though it gives your a nice system as a set of goals you can follow along with a companion mobile app. In my opinion, it’s much nicer to have good ideas under one cover than scattered around the Internet.
My score 4/5 due to how actual this topic is for myself
There’s a relatively short list of books I would like to keep on my desk. Most often those books are references and a composition of famous quotes. After I’ve read this chap I’d like to have it on my work desk at any moment.
This book is a perfect mix of lots of useful technical insights, practices and recommendations got from the author’s hard-earned experience combined with some of the soft-skills you need to make your software and its maintenance (which as the author states costs more than the initial 1.0 version) as smooth as possible with as much of interrupted sleep as you could possibly get.
The book is definitely outdated, some of the references to particular technologies look odd and obvious (if not even funny). Nevertheless, I will put this book in one row with the “SRE book” & “Project Phoenix” as it combines them both.