After spending some time reading through “Software Engineering at Google”, I have noticed that a lot of the information is not strictly about writing code. A decent number of chapters in the book are actually written about organizing and structuring large projects.
It helps to have a good team when the scope of work becomes very large, and the book spends multiple chapters talking about what makes a software engineering team productive. I specifically liked the section about anti-patterns, or patterns that are common in less productive teams. I think these kinds of negative patterns are often overlooked in team dynamics, and it is important to keep them in mind.
One anti-pattern that was discussed was avoiding discussing human issues within the team. It is really easy to decide that technical issues are the only thing that matters, but often times this is not the case. When team members are having human issues that are getting in the way of being productive, a team will not be very effective.
ChompingTheBit 