It’s right in the name
Development.
“What kind of development?” you ask.
Test-driven development. TDD for short.
I hear developers say they don’t have time to write tests. Sure, but you do have time to rewrite it three times and fix the production bugs, but whatever.
Regardless, TDD isn’t “writing tests.” Sure, you produce artifacts called “tests” and run them with testing libraries, but you’re just writing little scripts to exercise parts of your program. Because it’s way faster than manually running your program every time you make a change. And computers are a lot better at comparing values than you are.
Oh, and it helps you discover a usable design for your program too. And that’s probably the biggest win.