Max is a startup software engineer. He seeks to use what he has learnt as a startup founder and tech community leader to solves hard problems with innovate products or services.
Having test cases is important and it's useful in a DevOps perspective due to reliance on automating the small stuff which includes creating testing pipelines to test your code without you running it yourself.
As for TDD, it depends on your company or organisation engineering practices. They might require you to do it and you can do it to affect yourself. Ideally, I would go for TDD and as others have mentioned it's really subjective. Since there will be a need to write code that requires you to get it out as soon as possible. Especially you are creating a prototype or MVP who has a very short timeline for it to be completed.
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.
Having test cases is important and it's useful in a DevOps perspective due to reliance on automating the small stuff which includes creating testing pipelines to test your code without you running it yourself.
As for TDD, it depends on your company or organisation engineering practices. They might require you to do it and you can do it to affect yourself. Ideally, I would go for TDD and as others have mentioned it's really subjective. Since there will be a need to write code that requires you to get it out as soon as possible. Especially you are creating a prototype or MVP who has a very short timeline for it to be completed.