Team Geek by Brian W. Fitzpatrick

Team Geek

As a software engineer, you're great with computer languages, compilers, debuggers, and algorithms. And in a perfect world, those who produce the best code are the most successful. But in our perfectly messy world, success also depends on how you work with people to get your job done.In this highly entertaining book, Brian Fitzpatrick and Ben Collins-Sussman cover basic patterns and anti-patterns for working with other people, teams, and users wh...


Details Team Geek

TitleTeam Geek
ISBN9781449302443
Author
Release DateJul 21st, 2012
PublisherO'Reilly Media
LanguageEnglish
GenreNonfiction, Computer Science, Programming, Business, Management, Science, Technology, Leadership, Software
Rating

Reviews Team Geek

  • Rob
    1970-01-01
    People are basically a giant pile of intermittent bugs.With this simple humorous statement, Fitz and Ben [1] perfectly capture the attitude that leads us to need a book like Team Geek (O'Reilly 2012). It's not the only reason we need a book like this, but it's an important one, considering our target audience: otherwise high-functioning engineers that need a little help figuring out how to navigate the apparently volatile social landscape. And wh...
  • Mark Gibaud
    1970-01-01
    I was actually very disappointed with this. A lot of the information is pretty much common sense to anybody that has worked with any group of people in their lives, ie. Don't be a dick. The advice is very generic and I expected more insightful stuff from Googlers. Furthermore, the authors are rampantly guilty of using 2000 words when 200 would do. There is a lot of fluff in this book - I started skipping sentences and then paragraphs and then pag...
  • Pedro Almeida
    1970-01-01
    Easy to read book. It's amazing how hard is to see the lack of HTR (humility, trust and respect) we have when working in software development industry. Recommended to egocentric developers!
  • Anton Antonov
    1970-01-01
    Team Geek is a perfect read for every software engineer, no matter whether working in a big or small company.The book revolves around authors’ careers as a software developers and later as a team leads/managers. As the authors’ careers, the book also progresses from team work to managing people (a lot on that).People may disagree with this book’s title since it says it’s focused on a software developer’s point of view, but actually focu...
  • Dominic Wong
    1970-01-01
    Office politics 101 for geeks
  • Pawel Dolega
    1970-01-01
    As many reviewers already mentioned - this is a fair book for entry level management / team lead role. Actually more for the latter. Although it's targeted for people working in any kind of organization (big or small) I actually think it's more meaningful for people working in medium / larger organizations (still people working in smaller organizations or involved, say, in open source project should find it useful).For anyone having at least some...
  • evan
    1970-01-01
    This would be a good first book on management for developers. After managing for the last 4 years or so, I didn't find the book particularly interesting or new; I often found it a little too proud of itself. I read this part of a manager book club at work; I enjoyed the conversation that came out of having read the book more than the book itself.The ideas that did resonate with me from the book that were either things I had distinctly thought of,...
  • Sergey Teplyakov
    1970-01-01
    Неплохая книга, но в ней, все же, достаточно много банальностей.Ключевая книги заключается в том, что в основе любых отношений должны лежать три принципа - скромности, доверия и уважения, и что их наличие позволит устранить конфликты, сделать друж...
  • Martin
    1970-01-01
    Despite previous comments that the things in this book are pretty much common sense, I think there's a lot of valuable information on communication here - one has to realise that a lot of programmers are socially awkward to begin with, and not everybody reads self-help and communication books. So, more books like this are needed. That being said, the rules in this book could apply to any kind communication, not just the software-related one.The o...
  • Roman Pichlík
    1970-01-01
    The central theme of this book is HRT (Human, Respect and Trust) principle applied to all areas of geek's life - co-working with people, communication with users, leading people, dealing with boss etc. Geeks are really good in communication with machines but fail in face of communication with other people. This book helps understand it and gives you good tips&thoughts.
  • Srđan
    1970-01-01
    I would recommend this book to any developer or development manager. It provides both high level ideas and detailed examples of communication and behavior in development teams that make a healthy culture. Even if some of these ideas seem like common sense, or you're already aware of them, it's good to remind yourself about them and assess how successful are you in implementing them.
  • Marco Emmanuel Patiño Acosta
    1970-01-01
    This was a book I needed to read earlier. It was a great book with lots of advises, dos and don'ts for effective communication and collaboration. it has also a lot of examples I could relate to and advises to handle situations that worked in Google, SVN and other teams. Finally the great surprise was the final list with reference books to read more about the subject. I recommend this book a lot.
  • Ho Vu
    1970-01-01
    This is a very useful book for software engineers regardless of their positions. In fact the HRT(humility, respect, truth) principal described in the book is applicable to any team. The book is written in very clear simple language backed with many humorous stories that make it a quick and enjoyable read.
  • Niclas
    1970-01-01
    If you work in the software industry, you should read this book. It has clear, concise and actionable tips on working well as a team member or leader of an engineering team and also describes how to fit into the larger puzzle of a software org.
  • Brett
    1970-01-01
    The first chapter of this book is worth a read. The rest is meh.
  • Tomas Janousek
    1970-01-01
    Mandatory reading for everyone in the software industry.(I would've given it 5 stars had the authors not mentioned the Linux kernel community as a bad example.)
  • Ammar Lakis
    1970-01-01
    الكتاب رائع في استعراضه لكيفية التفاعل مع الآخرين ضمن بيئة العمل و اتخاذ القرار المناسبيجب أن يقرأه كل من لديه اهتمام بتحسين عمله الجماعي .. و مهندسو البرمجيات بالأخص !
  • Stephen Mullins
    1970-01-01
    This is a short but impactful book describing effective software engineering people skills. Most of this aligns to the culture at my current company (Signal) which is awesome. I wish I had read this much earlier in my career as it would have helped me better understand what kind of culture to establish within a team.While the book is filled with software engineering anecdotes, there is a certain universal message and appeal for the contents in th...
  • Mina Soare
    1970-01-01
    Management in a nutshell for all geeks everywhere. Really.Do you feel like management/leadership are buzzwords associated with someone stealing time for The Art of [insert what makes you happy, here] with endless meetings?Do you get a cramp in the glutes when someone speaks about “team culture”?Here’s a compact version of management know-how for science types everywhere. It’s just a different type of programming language. Really. Ignore t...
  • Dmytro Chasovskyi
    1970-01-01
    I found this book as an amazing resource of inspiration and new ideas. HRT principle is the key in figuring out in-depth problem into company, team and human-to-human relationship. I recommend this book to everyone who either considering moving to leading position and to anyone who want to advance their career or rethink current state of being inside an organisation, life, etc.
  • Abhijith
    1970-01-01
    This book is a good guide on the dynamics of a high functioning software development team - how individuals are supposed to work together to make great software. What works, what does not and so on. The chapters follow an ordering of stuff to be applied at the level of individual->team->organization->users. [Kinda like those books on networking where they deal with each layer of the stack :-)]
  • Jevgenij
    1970-01-01
    Advice is trivial and common-sense, details are absent.
  • Anton Onyshchenko
    1970-01-01
    The book is short (which is good), but full with some good advices which are applicable in any kind of human relationship.
  • Hunter Lee
    1970-01-01
    Want to read again next year!
  • Julaine
    1970-01-01
    Excellent. Full of good advice.
  • Nazim Elmazi
    1970-01-01
    It's marketed as a "software book," but this is one of the best books I've read on working with people in general. The style is wonderful, and the advice seems excellent.
  • Aarón Delgado
    1970-01-01
    It's a simple but useful guide of how to deal with a programmer's team work. Also it show author's anecdotes of the big tech companies. If you are in a startup or a company you should read this book.
  • Mehdy Khoshnoody
    1970-01-01
    Everyone who is remotely related to developing software must read this at least once a year!
  • Rod Hilton
    1970-01-01
    I think most software engineers have an ideal day, and it likely involves spending 100% of their workday in their IDE. No opening up e-mail, no chat, no IM, no meetings, no planning, no retros. But as fun as that can be, a huge part of professional software development involves working with other people. Team Geek is all about those moments, and how to be effective during them.The book is just full of good, solid advice for programmers. It's writ...
  • Mari
    1970-01-01
    Team Geek is a light and fun read with insightful commentary on how marrying the human “soft skills” with the technical “hard skills” can create the foundation for a great team. While Team Geek is written for software engineers (and their managers) in mind, its takeaways are relevant to anyone — engineer or non-engineer, lone wolf or team player. Though common sense at times with lessons already picked up from experience, what makes thi...