"I simply haven't discovered the right shape or form of the code yet" => totally agree with that. IMHO, TDD helps to find the shape. Writing expected results for test cases gives a part of the public interface.
In my experience, designing from the perspective of client code in general (of which the test is only one, and arguably the least important) is what leads to the best possible public interface.
Again, if writing the test first works best for you, personally, you should absolutely do that.
The larger point here is that not everyone has the same experience - so definitely try it, but don't force it. 🙂
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 simply haven't discovered the right shape or form of the code yet" => totally agree with that. IMHO, TDD helps to find the shape. Writing expected results for test cases gives a part of the public interface.
In my experience, designing from the perspective of client code in general (of which the test is only one, and arguably the least important) is what leads to the best possible public interface.
Again, if writing the test first works best for you, personally, you should absolutely do that.
The larger point here is that not everyone has the same experience - so definitely try it, but don't force it. 🙂