4 ms·

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 fi

by jaxn 9y ago

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 9y ago
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.