Re: Suggestion, advice on TDD adoption
"Adam Sroka [email protected] [testdrivendevelopment]" <[email protected]> Wed, 6 Apr 2016 18:25:59 -0700
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <CALaPUVfDFgDSLvkiQ2xDs_WYNm6aCnEwA7d4MttAdkpt_2u5mQ@mail.gmail.com> |
On Wed, Apr 6, 2016 at 6:01 PM, Russell Gold [email protected] [testdrivendevelopment] <[email protected]> wrote: > > > > On Apr 6, 2016, at 4:57 PM, Keith Ray [email protected] > [testdrivendevelopment] <[email protected]> wrote: > > It really really helps to have a coach working with your team and its code. > > > This is really a key. Without a coach, you are going to wind up trying > things, not understanding why they don’t work, and largely reinventing a > lot of practices. A coach can save you an incredible lot of time. You can > get some of it from books such as Robert Martin’s Clean Code > <http://www.barnesandnoble.com/w/clean-code-robert-c-martin/1101628669> (and > other books in the series), but a good coach is still much better. > > While I don’t disagree with this, the kind of coaching being described is expensive and people who can do it well are rare. It is very similar to hiring a senior developer—the one you want you cannot afford and the one you can afford you don’t want. You CAN do it without a coach. You can potentially avoid a number of pitfalls and delays with a good coach. It is a business decision whether the price of the coach is worth the reduction in risk.