Insanely good talk! Highly recommended and not from a TDD ivory tower, which is super important for people just starting out or in a TDD hole. I particularly liked the example of 'expected clapping' without giving instructions. Looking forward to more from you on this topic, Gui!
19:00 maybe there's a terminology issue here: the purpose of a test _is_ to fail, when the code doesn't work. but it's bizarre to design something to fail - no-one wants to make something that "fails"! so maybe we should say "trip" instead of "fail"? like an electrician might say "have you ever seen that circuit-breaker trip? that's how you know it works". if a circuit-breaker "fails" it's failed to detect a problem and is letting high voltage code into the production environment
Great talk. I used to think that in order to practice TDD I had to apply the principle to every types of tests and for every new method. Which kind of made me to quit doing TDD because like he said it broke when some behavior changed and it was super frustrating having to deal with not only the implementation but also the structure-coupled tests. Now I think I understand where exactly to apply TDD!.
everyone does talks like "how to fall in love with TDD" and "what went wrong with TDD". no-one talks about "adopting a cat with TDD" or "negotiating a car hire-purchase agreement with TDD". we're missing the middle of the story
Não costumo praticar TDD mas a tua palestra deu me muita vontade de o fazer. Obrigado 😊
Insanely good talk! Highly recommended and not from a TDD ivory tower, which is super important for people just starting out or in a TDD hole. I particularly liked the example of 'expected clapping' without giving instructions. Looking forward to more from you on this topic, Gui!
Gui's talk has been featured in the last issue of Tech Talks Weekly newsletter 🎉 Congrats!
19:00 maybe there's a terminology issue here: the purpose of a test _is_ to fail, when the code doesn't work. but it's bizarre to design something to fail - no-one wants to make something that "fails"!
so maybe we should say "trip" instead of "fail"? like an electrician might say "have you ever seen that circuit-breaker trip? that's how you know it works". if a circuit-breaker "fails" it's failed to detect a problem and is letting high voltage code into the production environment
Valid point
Great talk. I used to think that in order to practice TDD I had to apply the principle to every types of tests and for every new method. Which kind of made me to quit doing TDD because like he said it broke when some behavior changed and it was super frustrating having to deal with not only the implementation but also the structure-coupled tests. Now I think I understand where exactly to apply TDD!.
everyone does talks like "how to fall in love with TDD" and "what went wrong with TDD". no-one talks about "adopting a cat with TDD" or "negotiating a car hire-purchase agreement with TDD". we're missing the middle of the story
ok, Lion King is kind of a story about adopting a cat, if you look at it sideways
Scar did nothing wrong