I presented a session on "Essential Drupal Modules" at today's Boise Code Camp. The talk highlighted the modules most every Drupal installation should have, as well as a number of gap-fitting modules that fill a few UI and functionality deficits found in Drupal core. Additionally I included a segment on finding and evaluating modules.
The following is a posting of my code from this month's Boise Drupal User Group presentation I did on Drupal's Batch API as it exists in Drupal 6. It also showcases a simple technique one could use for firing off batch operations via Drupal's admin interface. It's light on prose, and heavy on code.
If programmers wanted to be technical writers, they probably would be technical writers and not programmers. You can see that tautology played out in many a Drupal module where the documentation (most likely a README.txt) is on the light side, and the code is on the heavy side. Don't get me wrong, there's some great documentation out there, and many valiant efforts on the part of developers, but you just can't always depend on extensive documentation - especially when you're looking at a module that's not particularly mature.
I'm setting up a new MacBook Pro for development work. Thought it might be nice to have a list of programs installed and customizations made. Perhaps others will find it helpful, too. This setup is fairly well road-tested by this Drupal and web application developer.
Find these via https://addons.mozilla.org/en-US/firefox/
Until recently, I worked for the Idaho Commission for Libraries as a web developer engaged with a number of projects based on Drupal and a few custom coded apps. It was a job I held for about eight years, starting as a part time grant funded assistant to the library networking consultant. As my skills increased, the agency's needs grew, and the Internet germinated, and it became a full-blown web designer and state employee position. A few years later I was reclassified as a developer.