Monday 3rd of December 2018

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…

And then the first real cusomer walks in and asks where the bathroom is. The bar bursts into flames killing everyone.