This is a good thing to do ("ask people for opinions before you start"), it just solves a different problem.
Btw I did something similar to the certainty score thing. We had a table with technical decisions ("let's refactor X in a certain way", "let's choose Y as the config format") and made predictions before implementing the decision. For example, "this will turn out to be shit, here's why" or "this is great and will work exactly as expected". The table was short-lived but pretty effective at teaching me that my technical decisions can be surprisingly bad.
2 comments
[ 5.3 ms ] story [ 18.0 ms ] threadI mean maybe those tests you are writing really aren't useful - not all testing is - why not get some opinions on it immediately before you start?
Btw I did something similar to the certainty score thing. We had a table with technical decisions ("let's refactor X in a certain way", "let's choose Y as the config format") and made predictions before implementing the decision. For example, "this will turn out to be shit, here's why" or "this is great and will work exactly as expected". The table was short-lived but pretty effective at teaching me that my technical decisions can be surprisingly bad.