Tal Doron Principal Software Engineer @ NICE I remember saying it over and over again, and always feeling like something is just not right. “I’ve finished, it’s working.. only tests left”. Why do I write tests if the task is finished and works as intended? And why is it considered to be a pain to many developers? In this session I’ll be showing the solution to the conflict above, which requires a shift of mindset towards TDD. I’ll be live coding the famous Bowling Kata while letting the tests(use cases) drive my design and implementation so that once the code is written and working, the task is actually done. Other talks at this conference 🚀🪐 https://www.conf42.com​/js2021 — 0:00 Intro 0:26 Talk