u/MMDB_Solutions

Obviously you want the best possible content for your top products, which almost certainly mains careful human curation of that content.

But for the rest, the other 80% that have little to no content, that are not in proper categories, and you will never have the time to update them all manually, have you had any success pumping AI content into them?

There are a lot of problems to avoid, trying to make it not really look like AI, avoiding repetitive phases or buzzwords, emojis, emdashes, etc, not to mention hallucinations. Have you had any luck with this, or have opinions on it's opportunity or appropriateness?

We have used TDD for lots of feature implementations, usually when we have a clearly defined set of business rules, and we're implementing a contained piece of logic that

However, we don't use it for everything. For hooking a lot of components together in an orchestration layer, we end up with a ton of mocks and setup code that end up being more code than we started with, and you need an expert on those tests to maintain them. Then god help you if you add a new DI constructor parameter, you're doing a lot of test updates.

Or if you're doing fast prototyping of what will eventually a solution, but you're moving large pieces around and adjusting the abstraction layers to find what fits the problem best. If you have to refactor a pile tests every time you make those adjustments, you'll never get anything built. In those cases, we usually go back and add tests after the fact once the design has hardened (but of course that may not always happen)

What rules do you use to decide why to use TDD or not? Especially, what guidance would you give to newer developers to on how to make those judgements?