Soft Skills: The software developer's life manual Paperback – January 6, 2015

For all of us who signed up for the author's e-newsletter, we all received an email regarding this comment:https://www.amazon.com/gp/customer-reviews/R1FJJTZWM2PA6E/ref=cm_cr_dp_d_rvw_ttl?ie=UTF8&ASIN=1617292397It sparked an interest in me, to see if that comment sheds another side of the coin regarding his soft skills book.And because I cannot write on that particular negative comment, I will post my views about the book and that negative comment here.I don't see his email as forcing us to downvote this comment.As a developer, I am sort of attached with the word "if"if (you disagree with Josh's low rating)downvote and write personal comment //suggestingelse//do whateverTherefore, his email did not force us all subscribers to downvote this. Though, intentional or not, the mail ignited a more thorough discussion regarding the book.About Josh's comment with the foreword, I could understand why he was disappointed with the foreword.Perhaps when we read books related to sw development, we are accustomed to read forewords that proved certain algorithm is optimal, that the theorem is factual because that foreword writer has similar study, or that the foreword writer has written a design that the author had implemented in the book, etc.However, this book is not a (brick and mortar) technical book. Therefore, we need to read this book (and the foreword) with different perspective or approach.I believe the foreword in question is fit and proper to his book. It narrated how the situation (publication deadline is looming) and Bob (as a busy person) had tested the author's soft skills, and how the author succeeded in receiving Bob's thoughts of the book and author's chance implementation of the book's content.I don't think Bob was coerced to write it. Although the foreword started as dark, it ended with a happier note that Bob had tested the contents of the book (see, it's somehow like a technical foreword indeed).On finding books that are more reputable and concise on the 7 topics mentioned, I still prefer to read this book because it is specific to my needs as a software engineer. I just ordered my book from Amazon Japan last week of April 2017 and I find the book straightforward and easy to implement for me. It saved me from a lot of TMI not applicable in my situation.It also helps to be a critical reader. There are some of the book that I don't agree. Not all in the book are trash, the book's content is not for everybody. But I can vouch majority of the book's content had helped me a lot.Nevertheless, I rather move on and read a new applicable/interesting chapter rather than dismissing the whole book as unhelpful.For me, I am thankful to find this book as it enriched me not just to be a better software engineer but a well-rounded person.

非常に簡単英文ですので英語の勉強とソフトエンジニアの生き方をユーモラスに両方学べます。

「ソフトウェア技術者が生きていく上で必要な知識のうち、技術書に載っていないものをひと通り集めてみた」という趣向の本です。PDFならば$10~20程度で販売されているので、ペーパーバックを買う必要は無いかと思います。