The good thing about digital photography is that releasing the shutter doesn't cost you money anymore. Just today I found the advice in a newsletter for photography classes that you should release the shutter often and capture as much as you can of "this special light" and "that special occasion" etc. etc.
Many photos don't cost money anymore indeed, but instead, they cost time, and they require more attention. We do have good software to help us with that, but it requires discipline if you don't want to get lost in your own giant stash of photos. Let me take this photo for example:
Skeletons (NIKON D700, 1/160s @ ISO 720; f/4, 120 mm (in 35mm)
It was made on a recent hike to Garnet Peak in Laguna Mountains - it's a nice spot, Laguna Mountains slowly rise up to something like 5500ft (about 1650m) from the coastal side, and then plunges down into the desert (Anza Borrego) in a rather steep drop. The views extend all the way to Salton Sea and are quite amazing in afternoon light. Most likely in the morning too. ;)
On the way to Garnet Peak, I passed by this group of dead trees. I found their pattern and appearance quite attractive, so I made a photo (duh, really?). It didn't turn out quite that good, I could immediately see that on the camera display - the sun was still too high up in the sky and the light too harsh (about 16:30).
At the summit of Garnet Peak, I've been using my polarizer, and because exposures can be somewhat tricky for the camera then, I usually switch to bracketing and make three exposures: normal, -1EV, +1EV (the D700 doesn't allow bigger steps than 1EV, it's quite a nuisance). I then pick the best exposure at home.
On the way back the light was far more pleasing (about 18:30 now), the camera was still set to bracketing, and when passing by these dead trees I made a set of bracketed exposures. Now the exposure count for
one and the same subject is at four already. And if you're like me, that's a rather mild example. Think of macros... many different attempts with different apertures, focal points, compositions, then throw in a bit of (bad) luck when shooting hand held and it's windy, and you end up with something like 20 or 30 shots of a single flower. Good thing they're patient.
When importing the photos to Lightroom, one step is to auto-stack multiple exposures by capture time. I then have a look at the best exposure, move it to the top of the stack, collapse the stack - and forget about it... I don't want to know how many useless stacks of photos I have on my harddisk because of that. It must be hundreds.
However, while evaluating the three bracketed exposures of the above scene, I got carried away on the overexposed version (because I wanted to see if it was still "good", highlight-wise) - and I overlooked that it is actually slightly blurry... because 1/80s at 120mm focal length can be tricky even with a stabilized lens when it's windy, and windy it was!
I didn't finish processing the photos that night and when I went back to them two days later, I had forgotten about that. I simply saw the version that was already "pretty good" and published it - to find out afterwards that I published the blurry version, because that's what I mistakenly started to work with. Needless to say that applying the edits to the correct photo and replacing it online took even more time. Embarrassing.
The lesson for myself is: select more radically, reject more radically, get rid of the bad ones more radically. And pay more attention to the details. :P
I browsed through my January and February folders in Lightroom to do exactly that. It's good to have a little bit of "distance" maybe, time-wise I mean. I was able to reject, remove and delete more than 600 photos from these two months alone -
six hundred! And I wasn't even overly hard on myself. That's something like 11GB of wasted hard disk space.
Funny sidenote: I submitted that photo to SeenBy, and it was rejected. When I uploaded it to
Flickr, the first comment from a fellow user was that he would love to have it as a print in the SeenBy style (behind acrylic glass). I would have loved of course to redirect him to SeenBy to get the print... instead, I just gave him the file. :P