This is very concise book for learning how to write and structure effective documentation as a developer. The book uses a fictional company’s product as a way to put theory into practice, by providing implementation examples along the journey. I found the book highly enjoyable and easy to read, it completely fulfill it’s purpose of introducing the reader to the world of documentation and provides references to dig a bit deeper if you are interested.

I’ll definitely recommend this book to my developer friends. Still, there are two notes that I consider important to know before reading it. The first one is about the perspective when writing documentation, it is commonly assumed that documentation is targeted for customers or external users, I believe this case will continue to exist but it will be increasingly common to have a need for internal documentation as we become aware of its benefits. The book mentions once or twice that documentation can be internal as well, and all of the content will hold true for internal documentation, but it is clearly written with external users in mind. Probably it is this way because customers would be part of any business plan and their needs are a fundamental part of any business being profitable, so those are very visible for executives, I would say internal documentation can have an impact as big for a company if done right because it can greatly improve efficiency, significantly reduce the time to market for new features, and as an added bonus, increase developers happiness.

A document is good when it fulfills its purpose.

In my opinion the book should start with the quote and probably with chapter 9, the one including it. It is not a quote from the authors but a quote quoted from another publication, still I think it is of uttermost importance when writing documentation, to answer the question: what for? And that is what my second comment is about, I would structure the book in a little different way. I think it would be super nice to have a TLDR; convention for books, but until that happens, I think one of the hardest parts of writing an educational book is to know in which order present the topics because you never know what readers will read.

I don’t consider the actual ordering to be bad, since it is a very hands-on approach, but from experience I would say it is often a good idea to slow down a bit and consider costs, in terms of effort, time and money, beforehand. So I would move the last three chapters to the beginning of the book. The audience depends on the purpose and the purpose often become very clearly defined when you try to measure quality, because, as the quote express, those are intrinsically related. Once you have an idea of the purpose and therefore the audience and the metrics you can think about the structure of the documentation, not from the writer point of view but from the consumer, and get a roughly estimate of the cost it will take to produce it, including the cost and effort to maintain, which is medium and long term and as a consequence easy to miss in all the excitement of joining a new initiative.

I often hear people saying that if it is needed it must be done no matter the cost, or even better, disregarding the cost, which often means not being fully aware of it. I find that a naive affirmation, and as it is stated in the book and in many other places, poor documentation is worst than no documentation.

Great book to learn a bit about developmental psychology. I really loved the way it presents information and the baseline idea that babies and scientists are alike.

Excellent book. The ideas and concepts presented are very interesting, useful and fact supported. Even if I don't agree with some of the conclusions, particularly the ones regarding social and political issues (I know, most of the book), I think it is a great starting point.

Not the kind of books that I usually read but it was ok, I think I learn a few things from it.

It was not what I expected, the book is very opinionated and biased against AI and machines. I didn’t expect her to be completely neutral, that would be really hard for any of us being humans but I did expect her to be a bit more fair given the fact she decided to write about this topic. It is not very technical but more of a moral reflection about modern world’s algorithmic tools, and as a consequence it is more appealing to people that share some common background with the author.


The book is divided in seven field chapters: Power, Data, Justice, Medicine, Cars, Crime, Art, and a conclusion chapter to close. I think there is a lot of overlapping among some of the chapters and others may not be as relevant. Through the book the author presents a lot of factual information about news and studies related to the algorithms in that field, but most of those are not new but the same ones that you can find in other popular books about algorithmic biases(I am thinking in Weapons of Math Destruction here).


I was really disappointed by the last chapters, and particularly the conclusion which I would summarize as a conservative call to regulate algorithms for the sake of humanity, understanding humanity not as a scientific feature but a spiritual one. Still I am trying to be fair, since the opinion part should be assumed from the How to be human in the age of the machine part in the title.


Nevertheless, and precisely because it is this lack of empathy she criticizes from algorithm makers and adopters, she should have tried to think that not all human share the same background and experiences regarding this topic are vastly influenced by geography, which is not just development indexes and access to the technologies but also the culture and social norms used to assess the outcome (just to be crystal clear, I don’t think algorithms are fair, I think humans are at least as unfair as algorithms because they are designed by them, a topic that is briefly discussed in the book but apparently vanished from the conclusions).


I won’t say the book is bad, most of it is interesting and well written, but I disagree with the reviews, and wouldn’t call it a science book or say it explains AI, machine learning or complicated algorithms. Although I enjoy it I would have not picked it, or said another way, I would have spent my time reading another book. I’ll let here two quotes that I hope will help you decide if it is the book for you.


But for me, true art can’t be created by accident. There are boundaries to the reach of algorithms. Limits to what can be quantified. Among all of the staggeringly impressive, mind-boggling things that data and statistics can tell me, how it feels to be human isn’t one of them.


The supermarket algorithm that robs a teenage girl of the chance to tell her father that she’s fallen pregnant.


An amazing book... I think it is a good reflection about our modern society, as relevant as 40 years ago when it happened. It not only discusses the local reaction about a cold blooded murder but all the facts that lead to it from a very human point of view.

It surely has some historical value, but I didn't like the book, it is build on stereotypes and I feel it a lot like perpetuating hate speech.

I love this book. It tells so much about the night, what does it means to the human and to the life on earth. Also it is a good book for planning a few trips around the globe. I choose this book randomly and end up with a lot of references for future reading.

I really enjoyed this book, it has the perfect balance between science facts and storytelling. I think it is a book everyone should read, we all live in a sexual world and it is sex what has shaped our modern society, not by itself but by every other aspect it is interlaced with.

I really liked this book, I think it's a nice interesting tale about how the world is and how it could be. Emphasizing that there are many happy events in our life even if we live in a hard world, and that most of it is as it is as a direct consequence of our actions.