> Any fad historians here? I got into the game late, but my impression is that TDD peaked when untyped interpreted languages like Ruby and JS were en vogue. Th

> Any fad historians here? I got into the game late, but my impression is that TDD peaked when untyped interpreted languages like Ruby and JS were en vogue. That was one of the first mistakes that began to spread everywhere and new engineers bought into the fads of using such unsound languages like JS, Ruby where it was difficult to reason with the type system to the point where they were testing the expected types themselves. In some applied uses such as backend systems, the fundamental design of untyped / dynamically typed languages can just let down the quality of the software in the first place and be a massive burden and cost on the developers to the point where they MUST use TDD no matter what even in greenfield projects. TypeScript has a more sound type-system, but still just serves as a temporary solution to the fundamental issues JavaScript always had and its still very easy to escape the type system and break it at runtime.