Testing things in isolation may give a better view of your APIs.
You know that "Play" with a little something on your IDE that runs only the tests? Do you know what it does?
A lot of people, when they start with TDD, get annoyed when you say that you may have to rewrite a lot of stuff, including whatever your already wrote.
"Things I Learnt The Hard Way (In 30 Years of Software Development)" started as a simple sequence of toots (the same as "tweets", on Mastodon when I was thinking about a new presentation I could do.
But why "a new presentation"?
"Without requirements or design, programming is the art of adding bugs to an empty text file." -- Louis Srygley
Don't know how to solve your problem? Write the steps as comments in your code.
Random thought about the previous post about "Things I Learnt The Hard Way".
This is a cynical, clinical collection of things I learnt in 30 years working with software development.
Again, some things are really cynical, others are long observations on different jobs.
In a previous life, I had a long discussion on why adding booleans was a bad idea. And just recently one of the core Python developers suggested the same thing -- adding booleans, that is. This is a long rant on why such things are bad.
GoodReads Summary: A comprehensive guide in developing and deploying high performance microservices with Rust.