HAMMERS AND NAILS
summary
A talk about how to choose which new development practices, tools or technologies to adopt by focusing on the problems they solve, illustrated with the presenter’s experience integrating a newly acquired team whose software practices differed from Audiense’s. It introduces systems thinking to analyze the broader impact of changing product development practices and offers a published matrix mapping common problems to typical solutions to help teams prioritize which changes to implement.
AI-written summary · about
chapters (9)
- 0:00Welcome
- 2:10Hammer bias
- 7:51Cultural differences in M&A
- 17:23Real problems first
- 19:29Systems thinking in software
- 27:20Modeling causal loops
- 35:59Tools for systems thinking
- 40:41Conclusion
- 42:05Q&A
related talks
01h 06mWhen everything looks like a hammer
54mFrom Software to Product Developers
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
32mPanel discussion: The journey to building effective engineering teams
43mThinking Architecturally
46mGood practices — why are they good?
41mSoftware architecture as a contributor to high performing teams
20mStrategies for engineering leaders to stay current and effective