> coach and mentor developers [rather than] vet their code. How do you teach these things concretely without discussing specific code? How do you tell if the l

> coach and mentor developers [rather than] vet their code. How do you teach these things concretely without discussing specific code? How do you tell if the lessons are sticking without checking their future work? Aside from that, neither TDD nor DevOps practices will get you idiomatic (relative to internally and externally) code, documentation, non-requirement performance worth a damn, test suites that are any good to begin with, etc. etc.. If you're running through a backlog of CRUD-ish features or whatever maybe those don't matter, though then I also wonder why the need for TDD instead of just a good CI pipeline.