The Thought Process Behind TDD (Test Driven Development)

Test Driven Development (TDD) is something that is quite polarizing in the development community. Some hate it, some love it and there is really no middle ground. Is TDD just a pure waste of time or does it actually save you time?
In this video, you'll find out that tests are not merely there to test the functionality of your code, but they can be thought of as a description of what the code should do - something like living documentation!
Go to my website for more information, code examples and articles:
● resocoder.com
Follow me on social media:
● / resocoder
● / resocoder
● / resocoder
● gab.ai/resocoder

[@RobertoIazzetta]

I'd love to see a real application (something like the Forcast App) wrote entierly in TDD. Great work tho, keep up!

[@RJ-bk2ho]

Love you reso!!

[@taslimfi]

This is what I'm waiting for..... Thanks a lot!!!

[@easazade]

i believe we can concern ourselves with multiple unit tests as long as they are testing a single behavior of a single unit

[@alirazaashraf8307]

It was helpful, Thanks alot.

[@orochimaruASH]

you're the best

[@hugosalazar6911]

If you had a Kotlin course, I would buy it. It would be my best investment.

[@shingiraibondai747]

You good bro, but i felt like you winding round n round. I failed to grasp the concept. Maybe an example will do

[@Halz0holic]

2:10 The probability of that you make some major mistake with TDD is really near 0% Get some real-world experience kid...