Hacker News new | past | comments | ask | show | jobs | submit login

That's potentially more helpful than writing the code itself. Writing unit tests can take most of the development time.



And literally throwing random half junk unit tests at your code will better test it than you writing unit tests that are blind to the problems it might have because you wrote both and both bits of code have the same blind spots.

We should probably be developing systems that fuzz all code by default.


I warmly recommend QuickCheck-inspired libraries.


In the future, code beyond all human comprehension will be rated for reliability by the number of layers of garbage unit tests it's buried under. Tests for the code, then tests for the tests, then tests for those te-...




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: