As usual, I don't really know how to rate this kind of book. It could be 3 stars, but I'm going with 4, if nothing else because there are no other books like this one.
The book is about how to write scientific papers, regardless of field. I picked it because it is organized as a very readable (to the degree possible) guide rather than a reference manual, which seemed more likely to work out in Kindle format. Despite best intentions, this is still surely a "eating a big plate of vegetables for your own good" kind of book. Not a summer vacation read.
I'm a pretty experienced technical writer, but I picked up some new ways of looking at things, which is all I really hoped for. I appreciated the treatment of how to approach the *act* of writing. I also appreciated that it established the mindset that clarity in technical writing is a skill that you can purposefully improve over time. It doesn't just fall from the sky for naturally gifted writers. You can accelerate your progression as technical writer if you are mindful about developing the skill.
One important thing that the book did is take concepts that I already more or less know (through hard-earned experience) and explain them in a way that I can now relate to others more clearly. It is difficult to guide inexperienced writers in a constructive way. A great example was the idea that an author should make a short thesis statement (not for the paper, but for themselves) and then weigh all of their technical content against whether it supports the thesis or not. This sounds trivial, but this is an easy to understand rule of thumb that can cut to the heart of a technical content debate.
Another example is the emphasis on the mindset of writing "for the reader". This also sounds trivial, but this perspective is a great way to help an inexperienced writer really understand why intricately ornate formal writing is counterproductive. You don't want to impress the reader with your command of english; you want them to grasp your idea clearly.
Also, simply put, I don't know of any other guide for scientific writing that is remotely like this one.
So what's the down side? First of all, the book is long. Maybe not in absolute terms, but in terms of how much time is spent on all topics, whether there is really anything meaningful to say about them or not. I enjoyed the book more once I let go of my guilt about skipping long passages. I also took several notes using the Kindle highlighting feature and emailed them to myself so I can review some key tips without digging for them again later.
Some topics seem to be covered for the sake of completeness rather than because there was anything truly helpful to say about them. For example, I skipped all of the discussion of how to choose the best word when you have several options at your disposal. That advice sounded more like a collection of platitudes than something you can really act on. I also skipped things like the addendum on beauty and humor in technical writing. That material could have been summed up more succinctly as: "This can be Ok in moderation, or not, whatever you think. Here are some clever examples I've found. You probably have to be a genius to pull this off."
I only found one thing that I outright disagreed with: the advice to proofread at the end of the day while you are tired. I couldn't disagree more. I proofread when I'm alert and have as much creativity as possible for restructuring difficult passages. If anything, use the evening to straighten out citations or get your formatting right, in my opinion.
So what would I want instead, if not this book? I guess I would just as soon have a few very short essays/articles about some of these topics that I could compile into my own list of required reading to suggest for others? But then again, this book wasn't custom written for me specifically.