I’ve never heard TDD described like this. I cannot even understand how this works from a project standpoint.
“We need a new feature. Todd’s written the test already, so everyone just have at it with your fastest implementation; whoever passes first, gets to go to prod!”
It’s insane, but it almost makes sense. If you have good tests, code that passes them should be a good enough start. Spend good money on devs that can write said tests, and then you can use them to drive productivity evaluation for those who aren’t. As a bonus, if you need to “shed” “controllable” expenses, you can fire the cheap devs.
I’ve never heard TDD described like this. I cannot even understand how this works from a project standpoint.
“We need a new feature. Todd’s written the test already, so everyone just have at it with your fastest implementation; whoever passes first, gets to go to prod!”
Reminds me of MCMC sampling, or straight up rejection sampling.
It’s insane, but it almost makes sense. If you have good tests, code that passes them should be a good enough start. Spend good money on devs that can write said tests, and then you can use them to drive productivity evaluation for those who aren’t. As a bonus, if you need to “shed” “controllable” expenses, you can fire the cheap devs.
I hate it.