News for hackers. Stuff that matters.
Re:The Big TDD Misunderstanding by Existenceblinks on Monday March 21, 2022 @08:49AM (#30753480)
So currently there is no any approach that scale at all. Everyone will write test differently.

And that's why we have code review process, and senior software engineers?

---

EDIT: add an example

When you look at a body of function and think if someone else changes some codes and you will have a hard time figuring out what goes wrong, that, the time you need to add some tests to it. Often it's a function that took numbers of iteration to work as you expect, or a function that is not simple but look so easy you write it right in one go.

Re:The Big TDD Misunderstanding by devoutsalsa on Monday March 21, 2022 @09:11AM (#30753708)
I’ve never seen an approach that scales. Once a team passes a certain size, it all turns into a disorganized shit show. Communication is hard, and as the pressure to earn revenue intensifies, there’s less & less time or buy in for craftsmanship.
Re:The Big TDD Misunderstanding by Existenceblinks on Monday March 21, 2022 @09:21AM (#30753802)
Yep, true. I'm really familiar with the vibe of time-to-market vs not to fuck customers up. Modules that are directly related to values to customers get more tests.