[boxfoxdox1]

For me it was BDD rather than TDD that helped out more, add to that linters and such and it made many beginning development hurdles easier.

Other thing that made it eaiser us convention in naming ( the dont know what the function return part mentioned in text)

BDD was helping becuase it alllowed me to change the way I was solving a problem or building a feautre, where before I would focus on fixing or creating a smaler thing then moving to the next, nowdays I would mock and scaffold until I can see the direction that the code takes rather than what direction I think it takes.

Those tests I write I treat as utterly disposable ones only keeping those that are enough tied to business logic ( and the lack of it) that represent a living important part of documentation.

Only then as parts solidify I might opt to do unit tests, but all those I approach as BDD test but on a different scale/scope.

So as with everyting doing too much of something will end up creating more problems than not. But it takes time and effort to find that balance and I havent even begin to scratch the surface of it.