When You're Evil: Building Credibility-Based Relationship with Developers
Talkat CAST 2016 · on Wednesday, 2016-08-10· at 15:45· Fletcher Challenge Theatre (1900), Simon Fraser University Vancouver 515 West Hastings Street Vancouver, BC V6B 5K3·
summary
Frames credibility as a wager: every question, bug report or favor risks a little currency to buy future influence. Specific tactics include learn and pronounce names, use small talk to find shared interests and create a common enemy (deadlines, PM requests) to align goals. Tactical reciprocity shows up as holding low‑risk bugs for days to avoid a developer’s bug cap, bringing cookies or donuts to build goodwill, and feeding developers juicy puzzles so they fix issues and then pressure peers to follow.
AI-written summary · about
chapters (19)
- 0:00Intro
- 7:35Group Bias
- 13:48Reciprocity
- 17:48Mastery
- 22:08Super Tester
- 23:26Bad Developer
- 27:23Resources
- 29:08Credibility
- 30:58Credibility in a team
- 33:36Credibility issues
- 36:51Brushing off developers
- 38:08Trust and Credibility
- 41:13Example of someone seeing through the facade
- 44:25Example of seeing through the facade
- 45:07Out and out bribery
- 48:43Personality
- 51:09Ethics
- 54:30Integrity
- 55:20Metrics
related talks
46mWho Hurt You? Earning the trust of developers
23mHow To Win Designers And Influence Developers
41mEvil Tech: How Devs Became Villains
47mDeveloper under influence
20mIncreasing your influence through building a professional network
28mOne weird trick to becoming a better software developer
41mWorking With Developers: A Tester's Survival Guide
48mHow to Talk to Developers