- What is technical coaching?
- Technical coaching means experienced developers working alongside a development team and teaching technical practices such as TDD, pair programming and refactoring on the team's own code. It differs from classroom training because the practices are learned on real tasks, with immediate feedback. QMates does it from the standpoint of extreme programming, the method it also uses to develop its own projects.
- How does technical coaching differ from Embedded Teams?
- Embedded Teams brings full-time QMates developers into your team, who deliver with you and pass on their method for the length of the project. Technical coaching is more targeted and more occasional. It runs in sessions, on a few practices and with the people who have to adopt them, and the team carries on the rest of the work. The two formats can be combined, and coaching can follow Embedded Teams to support the practices once the team is working on its own.
- Does TDD work on legacy code too?
- Yes, with one extra technique. Before changing the code you write characterisation tests, which pin down the current behaviour and act as a safety net. This is the work we describe on the Legacy Code Refactoring page. Technical coaching teaches TDD on new code and on changes, and points you there when legacy is the main problem.
- Doesn't pair programming double the cost?
- Two people on one task write fewer lines an hour, but they review each other's work as they go, share knowledge and make design decisions together. In our experience, the time you win back in code review, defects and handovers makes up for the time spent in pairs. During coaching we show when pairing pays off and when it is better to work alone.
- Do we have to stop delivering to do technical coaching?
- No. We work on the tasks already planned, so every coaching session also produces shippable code. Coding dojos and courses need dedicated time, and we agree it with you so that it doesn't weigh on the team's commitments.
- Does technical coaching work with our language and stack?
- Yes. Extreme programming practices don't depend on the language, and we work with the stack, tools and processes you already use.