The other problem is there is a megaton of lip service done to TDD.
You¡¯ll even have working tests. They make some framework change that breaks the tests, and they stop running them, or ¡°crunch time¡± comes, and management says ¡°I don¡¯t care if it takes longer next quarter, you need to get the following done for the end of the month¡±
Place after place I¡¯ve been in has a small to mid sized collection of tests, that are either not maintained, not run, or not added to, and when you do start adding, management complains.
I¡¯ve never been to a place that does more than pay lip service
--
73 de KG2V
Charlie
toggle quoted message
Show quoted text
On Nov 24, 2019, at 4:00 PM, Samuel ]slund <samuel@...> wrote:
?Hi all,
Spontaneously I would guess there is a difference in experience between us trying to learn TDD with 5-10 years or more of programming experience and loads of examples of why it was necessary, compared to people learning it today that (I hope) learn it earlier since TDD is not really new any more. I would also guess/hope that TDD now reach a broader range of people than those actively searching for ways to improve.
Regards,
//Samuel
