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

Sure, but what you're describing is prototyping.

Prototype all you want without tests, but once you've settled on a design & are ready to make it production-ready you should spend time at least writing unit tests for your work or (ideally) take what you've learned & re-apply to a clean design written in a test-first manner.

You might think this is a waste of time, but putting code into production without tests is going to give you more trouble in the long run.



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

Search: