2 for 1: How to be an Ally/Being A Better Ally
summary
A raw account of being called out in a women in tech meeting leads to concrete shifts: recognizes white male privilege as an actionable advantage, practices amplifying others and calling out bad behavior, swaps weeding out mentality for apprenticeship and internship hiring, replaces whiteboard stunts with job‑relevant take‑home projects, and cites the shock that women went from ~40% of programmers to ~20% as why systemic change matters. Concrete tactics, pitfalls, and real examples decide whether to watch.
AI-written summary · about
chapters (31)
- 0:00Intro
- 0:45Who am I
- 2:45Being called out
- 4:30Being blindsided
- 5:04Unconscious bias
- 5:46Guys reaction
- 6:49My aha moment
- 11:31Final Thoughts
- 12:56About Susan Wands
- 15:34Whats interesting to Guy
- 16:11How Guy met his parents
- 17:12Trailblazers
- 17:52Tech Stacks
- 19:06What happened
- 19:59Weed out class
- 20:52Weed out mentality in tech
- 21:28Why people leave tech
- 22:29societal issues
- 23:10coding jobs
- 24:24job descriptions
- 25:17skills
- 25:49code challenges
- 27:16internal environment
- 30:22micro regressions
- 32:22attribution
- 34:26weed out challenges
- 36:24companies getting hundreds of applicants
- 37:09Summer of Code
- 42:30Less selfserving
- 46:34Reaching out
- 50:03Weeding out
related talks
16mAlly for Women in Technology
21mHow I Strive to be an Ally Everyday
25mBe the Ally You Think You Are
34mMaking change as an Ally
46mBecoming an Ally
14mDiscover Allyship – taking action for a world where everyone feels safe, valued, and empowered
50mOvercoming your biases to be an effective ally
45mFrom All Sides: An Honest Conversation About Women In Technology