I think the same argument should be made for NOT writing tests for a prototype. ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

jaxn on July 16, 2017 | parent | context | favorite | on: Monolith First (2015)

I think the same argument should be made for NOT writing tests for a prototype.

Build something useful, fast. Then refactor. Write tests when refactoring or fixing a bug, but not when prototyping.

invisible on July 16, 2017 [–]

One issue with this approach is that refactoring can cause bugs or a change in behavior so you're risking bugs twice (initial write, then when doing refactor+teats). If you could guarantee the code was testable from the start then maybe this would help with the approach you outlined.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact