For the last two weeks we've been analyzing a program, written by an archaeologist named Michael Troyer, that measures commute times. So far we've admired the way in which its logic is split up, and have talked about how its error handling could be improved. In this final discussion of the program we'll look at how we can tidy up and significantly shorten the code that handles querying its database.
Read how on my blog.
Create your profile
Only paid subscribers can comment on this post
Check your email
For your security, we need to re-authenticate you.
Click the link we sent to , or click here to log in.