TDD is it worth it?

A talk about using TDD in Rails projects

Transcript

1. TDD is it worth it? Karthikeyan A K 77minds@gmail.com
2. Angry Developers • Takes 2.5 X time • Lot to code • Will client pay me so much? • Project profits? • Competition?
3. Why then TDD? • Is your client serious about the project? • Does he want the project to last long? • Does he wants his customers to be satisfied? • Is he willing to listen to you rather than code on his own?
4. Why then TDD? • If answer is yes to all the previous questions the go with TDD • Else drop project
5. What TDD demands? • Good Planning • Good Programmers • Patience • Coding Quality Improvents – Disciplined coding
6. How TDD helps you? • Refractor without much worries • Porting between Rails version becomes lot easier • No need to keep testing things again and again manually • Saves lot of time in the long run
7. Budgeting for TDD • Make client understand the following – What he thinks may be different from final outcome – What we programmers understand may be different from clients thought – So full estimation and budgeting may be a wrong idea
8. Go on agile • Take a small problem • Should be able to complete in a week • Do it and show it to client • Talk and put next weeks plan / problem • Repeat it
9. Payment • Get weekly payments • Document software as much as possible • Rdoc very important
10. No easy way out! • Computers may be science • Humans (clients) are illogical • Know to drop humans when they don't suit you
11. Questions? • I have right to keep silent!