When you recruited developers for your team, did you have the final word on recruitment? What level of involvement and decision making did other company stakeholders have?
In that particular company, yes, I did have the final word. It was a small company, a small team, and the director (who also had an IT background) gave me full trust. So, in that company, I had the final say on recruitment and on proposed architecture redesign. The hierarchy was like this - in that small company: (1) Director, (2) I, as Team Lead, (3) Developers. However the Director was hands-off when it came to day-to-day operations, so I had highest degree in that company (compared to other companies I worked in).
When you recruited developers for your team, did you have the final word on recruitment? What level of involvement and decision making did other company stakeholders have?
In that particular company, yes, I did have the final word. It was a small company, a small team, and the director (who also had an IT background) gave me full trust. So, in that company, I had the final say on recruitment and on proposed architecture redesign. The hierarchy was like this - in that small company: (1) Director, (2) I, as Team Lead, (3) Developers. However the Director was hands-off when it came to day-to-day operations, so I had highest degree in that company (compared to other companies I worked in).
The hardest part of TDD isn't writing tests - it's the people.
Yes, the hardest part is getting developers to switch to formalizing requirements as tests instead of jumping into code.