There are three points here:
1 Programming is just a small part of software development and so techniques like pair or Mob programming make perfect sense.
2 TDD is another way of acknowledging the importance of all the stuff that isn’t programming (which is also likely to change in the future).
So “measuring” 2. is simply measuring the consequence rather than 1. which is actually the real issue (that lots of “programmers” fail to grasp).
3 Code coverage is a measure of confidence that can be derived from the ongoing practice of TDD.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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.
There are three points here:
1 Programming is just a small part of software development and so techniques like pair or Mob programming make perfect sense.
2 TDD is another way of acknowledging the importance of all the stuff that isn’t programming (which is also likely to change in the future).
So “measuring” 2. is simply measuring the consequence rather than 1. which is actually the real issue (that lots of “programmers” fail to grasp).
3 Code coverage is a measure of confidence that can be derived from the ongoing practice of TDD.