Team Geek: A Software Developer's Guide to Working Well with Others (英語) ペーパーバック – 2012/7/21
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
Brian Fitzpatrick leads Google's Data Liberation Front and Transparency Engineering teams and has previously led Google's Project Hosting and Google Affiliate Network teams. He cofounded Google's Chicago engineering office and serves as both thought leader and internal advisor for Google's open data efforts.
Ben Collins-Sussman, one of the founding developers of the Subversion version control system, led Google's Project Hosting team, and now manages the engineering team for the Google Affiliate Network. He cofounded Google's engineering office in Chicago and ported Subversion to Google's Bigtable platform.
|星5つ 65% (65%)||65%|
|星4つ 28% (28%)||28%|
|星3つ 3% (3%)||3%|
|星2つ 0% (0%)||0%|
|星1つ 4% (4%)||4%|
Software is, despite appearances, a very human endeavor. From the outside, looking in, it may seem like software is built by typing code at your keyboard all day long. Arguably, typing actual code is a very small part of building and shipping a working product. Building software primarily involves effectively working with people from different domain and expertise. You could be talking to the customers or business analyst to understand the business domain and tease out the requirements. You could be working with architects, user experience team etc to come up with a high level design that underpins the development. You could be coding with or managing a team of coders, or you could be liaising with the test team responsible for QA. The pivot for all these activities is human interaction.
The crucial advice that keeps cropping up in this book in different shapes and form is that if you want to be a better software developer, architect, team leader you need to master the human element of software development. It is not a panacea but I would definitely recommend it to anyone who want to make themselves and their teams more effective.
I don't like the title, because I don't feel an association to the "geek" thing. I'm not attending sci-fi conferences, don't do mathematical calculations in my head and basically don't relate to nerd or geek culture or the stereotypes around it. With this in mind, I can confirm that after reluctantly looking past the title I found this book to be one of the best I have ever read about teams.
Don't be put off by the title if you don't feel you belong to the "geek" movement, this book is ace.
The book made me to realize that being Humility, Respect and Trust is not so easy. HRT is very critical to lay the foundation of a success development team.
The authors really know what they are talking about and there is no exaggeration happening in the book, just a very nice steady flow of info coming in and everything is being told in such a way which takes you on a journey and in the end you just close the book and start clapping with your hands giving the authors an firm applause for what they've accomplished with this book
Ce n'est pas vraiment un livre que l'on peut lire vite mais les nombreuses illustrations en facilite l'approche
Ils justifient aussi leur style de vie: humilité, respect, confiance.
un livre à avoir impérativement sur son Kindle ou sur sa table de chevet.
Weaknesses: Much advice is based on utopic premises, i.e., oriented towards large open source projects or Google (where candidates with dysfunctional team culture are theoretically weeded out during job interviews). It would be good if there was more realistic advice that applies to the 99% other software companies, e.g., where customers are government, military, etc. and companies are small businesses operating outside of silicon valley without the biggest talent pool.
There are a lot of common sense things contained in here, however, because of the personality types that gravitate towards IT/software it sometimes feels like we live in a different world and normal rules don't apply. It commonly feels like if we wait long enough, since most of us are non-confrontational, our social infractions will fix themselves or go away. That's rarely true and can eventually lead to unsatisfying work (and who wants that?) and burnt bridges.
Being a person that loves my career cocoon I've created in development, I found the section that urges the reader to break out towards leadership - a swift kick in the pants. It might take more planning, but I see value in their argument, "Your career is in your hands".
These tips help getting along in any walk of life. I am just glad they came from the perspective of seasoned software pros whom I can empathize with.