I use TDD at work for bug fix tickets specifically. This seems to mesh nicely with the way my brain approaches code. When I'm adding a feature, I often mess around a lot before I can really articulate to myself exactly what I am trying to do. Whereas with bug fixes, writing tests often helps me identify exactly what the problem is.
It's been a while since I did a refactor-only ticket as opposed to rolling refactors into some other work, but it seems like the TDD approach would be good for refactors as well.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I use TDD at work for bug fix tickets specifically. This seems to mesh nicely with the way my brain approaches code. When I'm adding a feature, I often mess around a lot before I can really articulate to myself exactly what I am trying to do. Whereas with bug fixes, writing tests often helps me identify exactly what the problem is.
It's been a while since I did a refactor-only ticket as opposed to rolling refactors into some other work, but it seems like the TDD approach would be good for refactors as well.