Keynote: Strategies to Cope With Conflicting Design Patterns in C++ Development Teams
summary
Practical claims: a single-session intervention reframes code‑review anxiety and yields clinically significant increases in engagement; use IDE search scopes and breakpoint tricks to inspect running state and avoid recompiles (presenter claims this beats 90% of peers); keep a written ladder of hypotheses and “parked” next steps to speed restarts; large rewrites can work if the author owns fallout and submits tidy, consistent 150-file PR style changes; train psychological flexibility (acceptance and commitment) to reduce avoidance and preserve long‑term code health.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:02Legacy code challenges
- 8:02Coping with legacy code
- 11:56Mindset shifts
- 16:30Building team support
- 20:45Pragmatism vs perfectionism
- 25:00Understanding burnout
- 37:07Debugging large codebases
- 47:18Feeling ineffective
- 56:02Accepting imperfect systems
- 1:01:18Influencing others' code
- 1:03:46Speaking and community
