Re:Ask HN: Do you write tests before the implementation?
by pubkraal on Friday November 15, 2019 @08:47AM
(#21544693)
I believed it until your password remark. That's a bad, bad practice.
[ Parent
| on HN ]
Re:Ask HN: Do you write tests before the implementation?
by kungtotte on Friday November 15, 2019 @09:25AM
(#21545013)
Even with a password manager?
Re:Ask HN: Do you write tests before the implementation?
by bransonf on Friday November 15, 2019 @09:46AM
(#21545188)
Enlighten me, why?
Re:Ask HN: Do you write tests before the implementation?
by kube-system on Friday November 15, 2019 @10:09AM
(#21545385)
Not sure I'd call it a 'bad bad practice' for a user to do it voluntarily, but it's unnecessary.
I think the above commenter is thinking about the requirement a user to change a password on a timed basis. There's been a good bit of research done in this area, and the consensus is that it just causes most people to stick a number at the end of their password anyway, making the policy completely worthless at best, but it often leads to people writing their passwords down.
Re:Ask HN: Do you write tests before the implementation?
by kaazhan on Friday November 15, 2019 @11:34AM
(#21546232)
Do you have a link to the research you're speaking about ?
My company is really about this kind of things and i'm not convinced it's really usefull
Re:Ask HN: Do you write tests before the implementation?
by kube-system on Friday November 22, 2019 @07:03AM
(#21604812)
It’s not research, but I would point them at NIST 800-63. These are well thought out standards that the entire US government follows. It would be tough to find a more comprehensive or authoritative source that says otherwise.
https://www.nist.gov/itl/tig/projects/special-publication-80...
Re:Ask HN: Do you write tests before the implementation?
by stjohnswarts on Friday November 15, 2019 @11:20AM
(#21546090)
Yeah I think it does more harm than good for sure.