Software Engineering At Google
Chapter #4 - Engineering for Equity (2 of 3)
Software Engineering at Google Chapter #4 - Engineering for Equity (2 of 3)
Engineering teams should be representative of their current and future users
Reject singular approaches as there are always different ways to do things
Re-evaluate existing processes
Design for a user who will have the most difficulty using your product
Exceptional engineers should bring diverse POVs into their lives and projects
At minimum an engineer needs to know the demographics of the population that he/she is writing software for
Engineering teams should be representative of both existing and future users of the product
Think about how your product can be an advantage to some groups and a disadvantage to others
Billions of people may use your product, consider the sway you have
Thank you for your time and attention.
Apply what you've learned here.
Enjoy it all.
© 2021 Josh Turgasen
All product names, logos, and trademarks are property of their respective owners