Not Just Code Monkeys
summary
Argues that developers must move from passive implementers to domain-savvy collaborators who propose and test ideas, citing an Amazon developer who ships a recommendation feature and runs an A/B test increased revenue to overturn product objections, and an early project where a demo plus SQL answers justifies the whole project. Calls out dark patterns like auto-added insurance and hard-to-cancel billing as ethical code responsibility, notes tech’s diversity gap—50% underrepresented—and urges engineers to address harassment and privacy failures.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:10Frustrations with agile
- 3:05Conversational stories in agile
- 6:20Developers need domain knowledge
- 8:54Rejecting dark patterns
- 11:21Software impact responsibility
- 15:18Tech society alienation
- 18:56Privacy and free internet
- 19:38Responsible developers
