Software Engineering at Google Chapter #2 - How to Work Well on Teams (3 of 3)

  • Code reviews help the long term sustainability of software
  • Blameless Post Mortems:
    • No finger pointing, find out what went wrong, and determine how to do better next time`
    • Document each post mortem using a template
  • Admitting mistakes or that you don’t know about something builds respect and trust over time
  • Be “open to influence”
  • The attributes and behaviors that Google looks for in a software engineer:
    • Thrives in ambiguity
    • Values feedback
    • Challenges status quo
    • Puts the user first
    • Cares about the team
    • Does the right thing
    • Understand and be aware of the working style of others. Don’t impose your style on them.
< BACK NEXT >
Tweet


   


   

Thank you for your time and attention.
Apply what you've learned here.
Enjoy it all.