One of my projects at work lately has been a searchable index of about 80,000 images, each involving about 20 fields' worth of metadata. It's a Drupal project, so it was pretty easy to set up the appropriate content types, fields, and so forth, but when it came time to set up searching, I made a few regrettable assumptions that cost me a lot of time.
Well, all this weekend's adventures seem to have paid off pretty well; I'm back now from DrupalCamp Austin and I thought I'd go ahead and review some of the things I took away from it all.
Following right on the heels of my weekend at DrupalCamp, I've stumbled across a few rather interesting blog posts on how Drupal is perceived in other parts of the PHP development community. Thought I'd post the links and make a few comments here, since the issues being discussed are pretty relevant to my day-to-day work as a web technology guy.
I've been having a bit of trouble getting prepared for my upcoming deployment presentation at DrupalCamp Austin, but I've found that when I write things down, it really helps me understand them better. So, without further ado and in no particular order, here are some of the most helpful things I've learned about the Drupal features module in the last few weeks.