14. Driving Technical Changes
How do I bring technical practices to my team? How do I convince my team to do Test-Driven Development (TDD)? How do I convince my manager to let us do pair programming? How can I introduce another language or framework in my current project? These are questions that always pop up during conversations with other developers. Over the years I found that convincing other developers to adopt technical practices and tools or change their attitude was far harder than convincing managers. Many developers suffer from what Kent Beck calls adolescent surety. They think they have the secret formula for delivering great software and nothing else is worth considering.
From developers to managers and architects, learning how to ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access