Robert C Martin - The Transformation Priority Premise

ROBERT C. MARTIN at NDC 2011
This just might be the thing that brings a mathematical rigor to TDD! If nothing else, it will certainly help programmers choose which tests to write next, and how best to make them pass. Transformations are like refactorings in that they are sim...

[@crabsynth3480]

Not sure how this talk remained hidden from me for all this time... thanks for the upload !

[@mansmor7211]

What a neat and clean explanation , God bless you,

[@kris1227]

Thank you Uncle Bob for the education.

[@a-petit]

Great material, thanks for sharing 🙏

[@bipintube2009]

Thank you Bob

[@vladimirbelokur602]

Super cool.

[@moriambar6533]

Never been able to extract quicksort from this. Feeling as stupid as a rock

[@DutchmanDavid]

The application that he tested is FitNesse, which is open source and can be found here: github.com/unclebob/fitnesse

[@bestintentions6089]

tests != qa ; tests = intent coverage

[@jurepustoslemsek7882]

I'm a very mathematical person, so this kind of work would infuriate me as I always want to *understand* what the code does and why it works. Nevertheless, I will adopt this kind of thought process.

[@ilyasabi8920]

It is actually mathematical process. The process of regression actually. You gradually fit it by using new tests as higher order of derivatives. You find the best fitting algorithm which uses the least amount of resources. You can probably automate it to a degree.

[@jlecordier]

The code does what the test are saying

[@karolyhorvath7624]

47:03 Bob, you're talking nonsense, go home.

[@anjanikumar745]

Why do you think so? I thought it was making lot of sense.

[@moriambar6533]

@@anjanikumar745 perhaps because it does not fall inevitably, and it's not so easy unless you know quicksort already.

[@BryonLape]

Uncle Bob's code better always work. Updating later by someone else is gonna be a real pain in the butt.