My question would be: in the prototyping phase where you're testing hypotheses, do you bother with documentation and tests, since they are likely to be changed/forgotten, and will slow you down?
Specifically for prototypes for checking factors like performance/reliability, I would implement automatic tests for a very limited slice of functionality that cuts through the layers.
For other prototypes to discuss the functionality early with users, I often found "throw away prototypes" helpful. So there, you would have no automated tests and no comprehensive documentation for these prototypes.
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.
Really like your answer!
My question would be: in the prototyping phase where you're testing hypotheses, do you bother with documentation and tests, since they are likely to be changed/forgotten, and will slow you down?
Specifically for prototypes for checking factors like performance/reliability, I would implement automatic tests for a very limited slice of functionality that cuts through the layers.
For other prototypes to discuss the functionality early with users, I often found "throw away prototypes" helpful. So there, you would have no automated tests and no comprehensive documentation for these prototypes.