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

Better still, implement one, assume it is broken, and find out why.


That's not a good advice. It is extremely hard to find problems in your own implementation, even if you're experienced in doing that.

Better advice: Find a mate (or a group), and find out why the other's implementation is broken. And go through some case studies first (see e.g. colin percival's postmortem in http://www.daemonology.net/blog/2011-01-18-tarsnap-critical-...)




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

Search: