Stateless Code | Why Test Driven Development? @StatelessCode | Uploaded October 2021 | Updated October 2024, 4 hours ago.
If you've watched any of the videos in the NerdDice series (youtube.com/playlist?list=PL9kkbu1kLUeOnUtMpAnJOCtHdThx1Efkt) you'll quickly notice that I expend a lot of effort on writing software tests. Why do that if your user is never going to directly experience the tests? If you have a project that lasts longer than 15 minutes, you're eventually going to want to make changes to it, and you want to be able to make those changes with confidence that you won't accidentally break something somewhere else.
In the Stateless Code videos, I try to follow an approach known as Test Driven Development as closely as possible. In that approach, you write the failing test first, then add in the code to make it pass, and then refactor the code as needed, ensuring that the tests continue to pass. If you ever have to hand off a project to another developer or have somebody join a team, they are going to have far more success onboarding if you have a healthy and robust test suite in place.
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
If you've watched any of the videos in the NerdDice series (youtube.com/playlist?list=PL9kkbu1kLUeOnUtMpAnJOCtHdThx1Efkt) you'll quickly notice that I expend a lot of effort on writing software tests. Why do that if your user is never going to directly experience the tests? If you have a project that lasts longer than 15 minutes, you're eventually going to want to make changes to it, and you want to be able to make those changes with confidence that you won't accidentally break something somewhere else.
In the Stateless Code videos, I try to follow an approach known as Test Driven Development as closely as possible. In that approach, you write the failing test first, then add in the code to make it pass, and then refactor the code as needed, ensuring that the tests continue to pass. If you ever have to hand off a project to another developer or have somebody join a team, they are going to have far more success onboarding if you have a healthy and robust test suite in place.
This video is CC0 - No rights reserved. (YouTube doesn't allow this option when publishing.) All code is released under the UNLICENSE. Stateless Code denies the concept of "intellectual property". Copying is not stealing.
