News for hackers. Stuff that matters.
Re:Monolith First (2015) by jaxn on Saturday July 15, 2017 @11:28PM (#14780324)
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.

Re:Monolith First (2015) by invisible on Sunday July 16, 2017 @11:02AM (#14782243)
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.