A recent post by
Derek Parker introduced me to
advisory locks in PostgreSQL.
Advisory locks are a very straightforward way to prevent multiple instances of a program from running at the same time. However, there are some cases when you shouldn’t use the database to enforce this constraint.
The stupidity of this is mind-boggling. Essentially, LinkedIn is asking you to insert a man-in-the-middle IMAP server that parses ALL your email and modifies the body so as to ‘enhance mobile email, giving professionals the information they need to be brilliant with people.’ The following tweet from Justin Miller first brought this to my attention:
Imagine, for a minute, that you’re an astronaut. On the ISS. Conducting a space walk. There you are, outside your vehicle, and you realize your spacesuit is leaking. You could drown. In outer space.
A Syrian fighter jet apparently dropped a napalm bomb on a school playground. Tragically, just another day in Syria. It’s images and scenes like this that anger me all the more when people tell me their opinions on foreign policy using statements like “Syrians are stupid.”
A handy wiki page that lists URL schemes being used by iOS apps is no longer being mantained. I copied the page over to this site in an effort to preserve the data and continue accepting submissions.
I recently needed to issue several dozen HTTP DELETE REST API calls of the form http://www.example.com/blah/n where n was a sequential version number. In this post I’ll show how to do this easily from the command line.
One of the features of Qur’an Memorizer, my first iOS app, is the ability to highlight a verse (ayah) when it’s tapped. To do this I access a database of verse x and y locations and retrieve the 4 coordinates I need to draw the resulting polygon.
The first version of the code released to the App Store looked a little bit like this: