Skip to Content


Book: Software Engineering At Google
  • An engineering decision framework that google uses is:

    • Category 1: Have-to-dos (Ex: Legal/Customer requirement)
    • Category 2: Best option (It’s the best option)
    • There should be no other categories
  • Google invests heavily in scalable policies.

  • The best option can be aided by having a conversion table in hand

    • Ex: Efficiency gains vs engineering cost + opportunity cost
    • This is only possible if everything is measured
  • Google uses artifact based build systems for every project

  • Google invested heavily in tooling to reduce developer effort

  • Google prevents haunted graveyard services through testing

  • Google optimizes code for human readability

Google, Large Scale Changes, Large Scale Code Changes,