Hacker News new | ask | show | jobs
by rooam-dev 2641 days ago
The goal is to try it as a team. Having 2 devs on a project with different approaches won't be efficient.

The part I strongly believe is that before writing a piece of code I need to know what I am writing. Similar to a task/story, I need to have an acceptance criteria. Knowing to write a test means knowing what are you writing.

Thanks for your input.

1 comments

> The part I strongly believe is that before writing a piece of code I need to know what I am writing. Similar to a task/story, I need to have an acceptance criteria. Knowing to write a test means knowing what are you writing.

Is there an existing problem in the team where people don't know what they're writing though?

I think at a high level only. Try and see how it goes (write some code, execute it and see the results) could be improved.