QA Testing

As a software developer I spend a lot of time writing defensive code: routines to check user input and handle it when it isn't what's expected. This blog post by Bill Sempf illustrates the kind of absurd lengths we sometimes have to go to if we want our software to be secure. I've reproduced some of the best responses here. A Quality Assurance engineer walks into a bar... orders a beer. orders 0 beers. orders 99999999 beers. orders a lizard. orders -1 beers. orders a sdhgahfgasjfasd. unhooks the tap and orders a beer. breaks all the glassware and orders a »