Rating: 
Summary: Bourgeois
Review: Fancy rubbish, is how I like to refer to this book. The author focuses on the sociological aspects of programming.In all honesty, this book will only be useful to good managers who actually care about their employees. Aside from that, it's useless. After all, it's quiet clear what the sociological aspects are: get the job done, or get out; we don't care if you hate cubicles, or want windows. Get Peopleware instead.
Rating: 
Summary: Good F/ S/W Pro(s) Who're Getting Into S/W Dev. Business
Review: From my experience in the S/W biz. this book has good advice for newbies who are getting in the biz. ... Topics ranged from ... SPO to basic project leadership skills. ... It reminds the reader that Good Software Development is based teamwork and that there is more than life than writing software code. ... (Which this book emphasize very heavily.) ... I do recommend it!
Rating:
Summary: Good F/ S/W Pro(s) Who're Getting Into S/W Dev. Business
Review: From my experience in the S/W biz. this book has good advice for newbies who are getting in the biz. ... Topics ranged from ... SPO to basic project leadership skills. ... It reminds the reader that Good Software Development is based teamwork and that there is more than life than writing software code. ... (Which this book emphasize very heavily.) ... I do recommend it!
Rating:
Summary: Therapy for post-dot-com mania.
Review: I first discovered this book thanks to the happy confluence of serendipity, perpetual bookstore browsing, and two decades of white-knuckling it as a software programmer. For the past few years it has given comfort and advice. Again today I am purchasing a copy as a gift for the shrink who is nursing me following the burst of the dot-com bubble. If I were on a desert island I would first wish for this book.
Rating: 
Summary: Interesting perspective.
Review: I found it crowded with good advice and ideas. I also found myself skipping and jumping around in it after a while, and putting it down altogether, because it was getting a bit tedious. But I would leave it lying in a visible place and pick it up again some evenings later. And every time I picked it up I found good and valuable advice in it. There are headings and subheadings on just about every page and the text under them is more or less self-contained: so it's amenable to browsing (chapter 1 excepted). And believe me, it has a huge amount of content. One of the things I like is its stated intention to make you a happier developer, not just a better developer. The causes of developer suffering and confusion are predominantly management and human issues, needless to say, since the machine and machine tools continue to be on their best behavior. The book has helped me avoid some suffering and confusion. It is not B.S.
Rating: 
Summary: Plenty of goodies, but also some aridities
Review: I found it crowded with good advice and ideas. I also found myself skipping and jumping around in it after a while, and putting it down altogether, because it was getting a bit tedious. But I would leave it lying in a visible place and pick it up again some evenings later. And every time I picked it up I found good and valuable advice in it. There are headings and subheadings on just about every page and the text under them is more or less self-contained: so it's amenable to browsing (chapter 1 excepted). And believe me, it has a huge amount of content. One of the things I like is its stated intention to make you a happier developer, not just a better developer. The causes of developer suffering and confusion are predominantly management and human issues, needless to say, since the machine and machine tools continue to be on their best behavior. The book has helped me avoid some suffering and confusion. It is not B.S.
Rating:
Summary: Thought provoking with good ideas
Review: I have really enjoyed reading this book. It is packed full of information. For example there are sections on personality types and problem solving approaches, as well as sections on creating teams from disparate personalities and the challenges of building teams. I found this book thought provoking and a good introduction to a wealth of information on sociology issues in software development. People issues are important in team development of software, and most of us will have to work in teams for a large part of our careers. The bibiography is large, good for following up on topics of particular interest. I don't expect to use everything in the book, but will pick and choose what is appropriate in each particular situation.
Rating:
Summary: Wonderful JAVA break reading.
Review: Java break, <groan> Oh - it's a bad pun. but with a subtitle of "A Sociology of Software Development" one would think this is a dissertation. May be it was. But it's a good read. However it may take several times to get the most of it. I recommend this for every software engineer. Managers buy it for the whole group, start them out with a plan, to develop as a person. David
Rating:
Summary: Wonderful JAVA break reading.
Review: Java break, <groan> Oh - it's a bad pun. but with a subtitle of "A Sociology of Software Development" one would think this is a dissertation. May be it was. But it's a good read. However it may take several times to get the most of it. I recommend this for every software engineer. Managers buy it for the whole group, start them out with a plan, to develop as a person. David
Rating:
Summary: Wonderful JAVA break reading.
Review: Java break, Oh - it's a bad pun. but with a subtitle of "A Sociology of Software Development" one would think this is a dissertation. May be it was. But it's a good read. However it may take several times to get the most of it.I recommend this for every software engineer. Managers buy it for the whole group, start them out with a plan, to develop as a person. David
| 
