Re:Ask HN: How can I convince a team member to try TDD
by rooam-dev on Wednesday April 10, 2019 @04:15PM
(#19628353)
My main goal is to improve our development process. I understand everyone is different and has their own ways, but if somebody doesn't use a tool at its full potential then in the end company/team loses, because instead of improving things, people fight/use less efficient process.
In this case I think TDD or a version of TDD acceptable to the team can really speed up development. I want that feeling if I run all the tests I can deploy.
All devs are remote devs with different timezones.
What concrete problems are you having that you think TDD is going to make better? Are too many bugs making it to production? Are you not writing enough tests? Are your tests poor quality?
I would have a bad reaction if somebody was trying to push TDD on to a project without objectively weighing up the benefits as TDD isn't suitable everywhere.
Instead of citing random articles, you should all work together to objectively weigh up the pros and cons for your team, then perhaps give a version of TDD a trial on a suitable small project or subproject.
If you can't convince people, maybe you're not selling the specifics of how it's going to help with the issues your team is facing or you haven't considered this aspect hard enough yet.