The Hardest Problems in Computer Science
summary
AlterConf Berlin 2017 material connects three programming pain points to inclusion: cache invalidation maps to dangerous assumptions about who belongs, naming maps to how identifiers exclude, and off‑by‑one errors map to token hires that isolate. It cites Kahneman, a Recurse Center social rule: No Feigning Surprise, a study that finds about 70% identifiers in code, and Terrell et al.'s result that gender‑neutral handles increase GitHub pull‑request acceptance, and offers concrete fixes like clearer names and hiring more than one underrepresented engineer.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:06[1] cache invalidation the problem
- 4:49[1] cache invalidation solutions
- 6:24[1] cache invalidation your thoughts?
- 7:10[2] naming the problem
- 10:01[2] naming solutions
- 11:22[2] naming your thoughts?
- 12:02[@] off-by-one errors the problem
- 15:17[@] off-by-one errors solutions
- 16:58[@] off-by-one errors your thoughts?
- 19:11Recording and Production Confreaks
related talks
07mHow to get more women to conferences like this
31mWorks On My Machine, or the Problem is between Keyboard and Chair
53mCoding Like a Girl
37mProgramming Diversity
16mInclusivity in the Hacker Background: Where We Are, ...
25mCognitive biases, blindspots and inclusion
25mAntipatterns for Diversity
42mProgramming Diversity