In Rails 2.0, ActiveRecord changed the default for per-request SQL query-caching to on. The cache caches the results of each SQL query made during the processing of a single request to the application; the cache is flushed after the request is completed.
Caching can obviously save trips to the database if queries are repeated multiple times in a request, so it makes sense to have it on by default. I ran into a problem which was traced to this caching behaviour the other day, so, as information on query caching seems to be spread across several blog posts, I thought I’d draw together the bits I found.
The Sony Ericsson w910i will not sync with iSync out of the box. This is very annoying! It is possible to get the w910i to work using a plugin for iSync, I found, as follows.
Update: I have found an alternative to the Feisar plugin: a chap named Andreas has written a free iSync plugin for the w910i. I recommend this plugin over the Feisar alternative as it works for me, it’s free and Andreas is planning to release the source code so we can make sure it does nothing nasty.
If you can read this, it means that the first stage of moving dx13 is complete: moving the current content to the new host and changing where the domain name points to. Great!
I finally have some control of my fate again. The dx13.co.uk domain has passed into the hands of my friend Jason, an able custodian if ever there was one. The previous person looking after the domain for me went missing in action sometime ago, which was rather worrying. Fortunately the domain was renewed last June when it came up for expiry by some mysterious entity. Needless to say, however, having a trusted friend looking after the name for me, able to point it wherever my whim desires, is most relieving.
A few months ago, there was a kerfuffle in the programming blog world about a little problem called FizzBuzz. Every now and then someone posts about their experiences interviewing candidates for coding positions. One such post was an example of a way to weed out the terrible developers from the merely not-that-good (i.e., the rest of us). It was titled Using FizzBuzz to Find Developers who Grok Coding and presented the following problem: