This gist is a fork of the gist from this blog post.

http://matt.might.net/articles/what-cs-majors-should-know/

• Read Hacking: The Art of Exploitation, 2nd Edition
• Read Gray Hat Python: Python Programming for Hackers and Reverse Engineers
• Read The Hacker Playbook 2: Practical Guide To Penetration Testing

This gist is part of a blog post. Check it out at:

http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer

Source: http://blog.8thlight.com/uncle-bob/2013/09/23/Test-first.html

• tests are specs for the system and are more important than the system itself
• (Tests should be) short, well factored, and well named. They ought to read like specifications; because they are specifications
• (Goal:) trust your test suite to the extent that, if it passes, you know you

I hereby claim:

• I am rvong on github.
• I am richvong (https://keybase.io/richvong) on keybase.
• I have a public key whose fingerprint is 9387 C3D7 8EC4 CEBB 4C53 D2DD E4FB 4794 6AFC 673C

To claim this, I am signing this object: