5 ms·

That is exactly my argument against Test Driven Development.

• marginalia_nu 5y ago
  I'm not sure it's that scathing. Tests may well be seen as a tool for granting access to a particular piece of logic and allow you to interact with it it directly, to ensure that the code remains sufficiently decoupled to allow this. In that case, they may aid in discovering and examining unexpected behavior. This isn't waterproof though. I think TDD-code prima facie upholds its promise to keeping down the code complexity per module, this is often at the expense of the bigger picture architecture. You go from spaghetti code to ravioli code; hardly an improvement.