I got nerd-sniped by a Reddit post on Test-Driven Development. Sorry in advance.

The RubyLA blog offers insights, tutorials, and community updates for Ruby developers in Los Angeles and beyond. Developers can explore Ruby language features, web development frameworks, and best practices for building Ruby applications. Additionally, the blog covers Ruby meetups, events, and job opportunities in the Los Angeles area, fostering collaboration and networking within the local Ruby community.

RUBYLAND

A developer explores a Reddit discussion about Test-Driven Development adoption, analyzing various perspectives on TDD implementation. The post examines common misconceptions about TDD, discusses the differences between frontend and backend testing approaches, and critiques AI-generated tests. Key insights include focusing on test failure cases, treating code as a liability, and understanding that TDD doesn't require knowing the implementation beforehand. The author emphasizes that effective testing should provide value and support code changes, while acknowledging that TDD isn't always the right approach for every situation.

Do you guys really do TDD?

In my experience no one does TDD. It’s a buzz word, it looks good on paper but in the real world slows everything down

I make sure to write my code so it is testable. I don’t do TDD, as I change the code a lot before I settle on the “final” state (due to prototyping and refactorings), and then I write the tests when I am happy with the code.
With TDD I feel I waste time on rewriting the tests all the time, before be code is in a good state. And I create the test units to ensure test coverage and so I can make adjustments to the code, and run the test to see if I broke anything.

Depends who’s asking. If you’re my boss, yes we do TDD with 100% coverage.
If you’re a fellow developer, then nah, we test some stuff if we feel like it.

Yes, because… why not? I don’t know why people don’t do TDD.
I make TDD tests to know what I expect from the code. And then I add code.
With AI nowadays it’s too easy to not to do. You can make test and then tell AI to write logic to pass the test.
Writing tests after logic is self-agreement and not the best. You know what complex things you had to do to make it work and now you just test ‘those things’, and many times you can stray away from what’s the real goal of the test.