Programmer’s Paradox

This is just a reminder that you should write failing unit tests first, so that when you forget

if __name__ == ‘__main__’
unittest.main()

in your test file, like I did, you don’t think everything is working because none of the tests fail.

I’m currently using Thrift at work.  It’s a convenient way to shuttle data across different services and to invoke remote procedure calls.  I like it because of how lightweight it is, so I don’t have to wrestle with code for a kitchen when all I need is a faucet.
The one downside to Thrift at the [...]

Let it be a lesson to me never to blindly follow a spec from Mozilla again, without first testing it in Internet Explorer, because of course Mozilla and Microsoft don’t implement a specification the same way, even if it is one as simple as open search.
There was a bug with the Lulu.com search bar with [...]

Last night I had a free evening, so I opted to do a project I’ve been meaning to do for a while: write the code needed to put a Lulu.com option in the search bar you likely see in the upper right corner of your browser.  It operates just like the Google option that is [...]

Recently I came across this eye opening post on testing.  I’d never thought about there being a fundamental difference in philosophies on testing before.
To be clear, when I write about testing in this post I am thinking specifically about test driven development, which is also what I feel David Christiansen is talking about in his [...]