Team Geek: A Software Developer's Guide to Working Well with Others

A handy guide of best practices for all stakeholders of a project. Revolves around simple, commonly accepted principles of being a good human being first with intention of delivering something useful for others.Recipe for channeling individual energies towards achieving the common goals, and increasing productivity by reducing friction.This book is applicable not just for software developers; but to any group of individuals having supposedly/ intended common goals, and having a potential for conflicts about how to achieve those while also guarding individual interests.It's déjà vu for experienced (> 7 years) folks. Listing of all the best practices in an organized manner in one place is the value of this book.Equivalent of the books 'Code complete', and 'Writing solid code' for nurturing great teams. Those two book had profound impact early in my career. I wish this book was available way earlier for me and to those I worked with so far. I would've named this book 'Team complete' or 'Developing productive teams'.Speaking in the software metaphor, I wish I could write a country specific localization of this book. While most of the ideas expressed are valid, some nuances of recommendations made do vary across world cultures, company type, and regions.Meaningful cross references provided at the end of each chapter. Good that they are hyperlinked in the soft copy form.Kindle edition likes: digital index of topics at the end of the book makes post-reading, future reference a charm. Also, hyperlinked cross-references provided at the end of each chapter.Gripes: two-column view was not available with Kindle for PC, though the reader supports it for other books.Glad that I read it: assuring that I was not alone to have some special experiences while doing productive work with people, that these are patterns, and that many of the antidotes have worked well for others, too. People with structured minds always like patterns, so that those can be tackled with some predictability ;-)

The book was quite an enjoyable read. The mere fact that I finished reading it was a good sign. The book kept me enthralled with its rich anecdotes even though they can be applied to pretty much industry. I really enjoyed the section about dealing with poisonous coworkers as this seems to be a common problem in companies. I also enjoyed learning about the HRT principle and how it can ensure a healthy culture within a software development team.I would recommend this book to pretty much any one but more so to software developers. It's a good refresher on how to deal with common problems within software teams and how to participate in or lead a solid, lean software development team.The books had some great points but I often thought that most of the advice and anecdotes were based on common sense. This is why I gave it four stars.

In short, read this book.I am one of those socially awkward programmers this book was directed at. When the author describes the person who would rather have an evening with a compiler than a average human, he described me. At first I was annoyed by how simple and well, not technical, his advice was yet I found it to be useful and insightful. There is nothing new in this book, but because it's said by someone who understands it gave some of these lessons more credibility in my mind. I often feel like a majority of people who would give me advice just don't understand or are relating things to me in a framework I'd rather just reject. A good example of this is how I view politics and "emotional maturity." I see it as a tool that people use to manipulate others and essentially lie to them. I hate it when I feel like I've been "hoodwinked" or lied to. The author puts forward a real good argument as to why learning to interact with others and play the game a bit can pay back in dividends. Refusing to interact with others out of principal is not the answer, regardless of how hard that is to accept. I may not change, but at the least I am once again reminded of how I should change should the need arise.

This is a short book that is quickly read. It has some good points, but brings nothing fundamentally new to the table if you have been paying any interest to agile web development the pas 5 years.

I found this book enjoyable and appropriate for helping me understand how to improve my "social graces" in my development team environment.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.

I've been a software developer for 5+ years, and I consider that this book goes straight to the point. It focus on the social skills one ought to master in order to be a sucessful developer - skills that most of us lack. It also gives precious hints to leaders - specially novice ones with a software development background. I'm yet to finish the book, but I already regard it as a must read to both rookie and experienced developers and leaders.

It gives a better prospective how to work with team members. One thing I can pickup is HRT principle: Humility, Respect and Trust which helps you working with team.

Enjoyed every word. This book shall be my bible ! A must if you want to grow personally and technically

I liked this book so much, that I'm actually going to say that it's there amongst one of the best books I had the pleasure to read.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

I say this with tongue in cheek, but I have a serious point to make. The brilliance of the book is inversely proportional to the brilliance of the title.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.

Les auteurs passent en revue la gestion de la collaboration (que vous soyez simple acteur ou teamleader)Ce n'est pas vraiment un livre que l'on peut lire vite mais les nombreuses illustrations en facilite l'approcheIls justifient aussi leur style de vie: humilité, respect, confiance.un livre à avoir impérativement sur son Kindle ou sur sa table de chevet.