Its definitely a bad idea writing new code that builds up on your old code, that has not been tested properly, because you quickly have to start debugging multiple layer is code at once.

you are viewing a single comment's thread
view the rest of the comments

[–] 9point6@lemmy.world 4 points 1 day ago (11 children)

Honestly this is the reason TDD is most important for personal projects.

If it's your job, the code isn't getting merged without decent tests. Yes you should probably write them first so you think about your implementation properly, but let's face it, many tests are written after in practice.

If it's something written in your free time, you're just not writing those tests most of the time if you didn't write them up front.

[–] BlueKey@fedia.io 2 points 1 day ago

I tried TDD in a personal project recently and it got annoying pretty fast. It was also a project where I tried a new Framework so writing test when one doesn't know how things behave exactly results in adjusting the tests afterwards anyway.
Thinkimg how I want to designe my API upfront while discovering the details as I go served me well in the past (still in context of personal projects).

It also doesn't help when my tests have more bugs than the tested code...

load more comments (10 replies)