I'm going with 'TTD' being a typo. If it's not then I don't even know what that is, let alone practice it :D
But TDD then also no. I love unit testing and it absolutely is an essential part of quality software. However, I've never actually worked anywhere that physically starts with the tests and then writes software to pass them. Even in places that claim to do TDD, it's always been software first and tests closely after.
To be honest, I feel that software development is a complex beast and it's difficult to write a bunch of tests first to then develop something that passes those tests. What you develop will likely need to change, sometimes part way through developing it (for many reasons) and it's just never been a practical way to develop, for me.
Totally agree, I usually do TDD for the most critical parts of an application, for example, the auth logic or logic where we handle users' Currency and so on...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm going with 'TTD' being a typo. If it's not then I don't even know what that is, let alone practice it :D
But TDD then also no. I love unit testing and it absolutely is an essential part of quality software. However, I've never actually worked anywhere that physically starts with the tests and then writes software to pass them. Even in places that claim to do TDD, it's always been software first and tests closely after.
To be honest, I feel that software development is a complex beast and it's difficult to write a bunch of tests first to then develop something that passes those tests. What you develop will likely need to change, sometimes part way through developing it (for many reasons) and it's just never been a practical way to develop, for me.
Totally agree, I usually do TDD for the most critical parts of an application, for example, the auth logic or logic where we handle users' Currency and so on...