thechrisproject photography

From Reuters’ document on Photoshop guidelines for their photographers:

ALLOWED:

Cropping
Adjustment of Levels to histogram limits
Minor colour correction
Sharpening at 300%, 0.3, 0
Careful use of lasso tool
Subtle use of burn tool
Adjustment of highlights and shadows
Eye dropper to check/set gray

NOT ALLOWED:

Additions or deletions to image
Cloning & Healing tool (except dust)
Airbrush, brush, paint
Selective area sharpening
Excessive lightening/darkening
Excessive colour tone change
Auto levels
Blurring
Eraser tool
Quick Mask
In-camera sharpening
In-camera saturation styles

Photographer/Blogger/Doctor (I think) George Barr put up an interesting post a few days ago about revamping his webpage. I started to reply but it got more involved than usual and I figured I’d continue the conversation here.

I’m a photographer by night and a web-developer (mostly programming, some design work) by day. My company writes fairly complex enterprise-level digital asset management applications so when it came time for me to redesign my website, it was almost a relief to try and assemble it in the most spartan way possible. I did it by hand in notepad and vi.

What I find utterly amazing is this statement from George:

I realized this was no walk in the park, but over three years I wrote my own medical office software including clinical notes, appointments, lab, documents and so on, all together more than 150,000 lines of code, so you’d think that I could put together a website.

As a professional programmer, I would tend to agree. Medical office software is something you typically buy from Medical Manager (now owned by Sage) or Epic Systems. Customized medical software would probably cost as much as a house. The fact that George wrote some by himself is indicative of the fact that he must enjoy doing it. I’d call it being a tinkerer. Doctors probably have a fairly good idea of what their time is worth and spending three years writing medical software is not something I think they’d do just to save a few bucks.

The question is this: is it worth it to do it yourself? I gather that George would like to display lots of images, say more than a hundred, and I also infer that he would like to be able to sell prints through the site. So you’re looking at a content management system with merchant functions and some UI customization options. You have to be able to make it look pretty.

George goes on to say:

I was aware that with hundreds of images and wanting to avoid fixed size templates, I would really need a database of images. Turns out that means I have to learn SQL, oh and PHP or such.

The first thought that springs to mind is, “You wrote medical office software and didn’t use a database?!” After thinking that over for a minute I addressed the next issue: databases aren’t the best place to store images. They’re actually pretty bad. Static files work better. You’re better off making 10 different sizes of image and storing it in the filesystem than… well, I don’t really know what the alternative would be. You could store a large-ish version in a database and resize it on the fly, I guess, but that really isn’t feasible. You’d be better off storing tons of different sized previews in the database, but then you’re not really gaining anything by using the database.

That’s not to say that a database isn’t necessary. Many content management systems use them. This Wordpress installation I’m using has a database. But you certainly don’t have to know any SQL to use it. You just need to have someone set it up for you and give you access. The Wordpress software takes care of the rest.

But I didn’t really start this post to babble about all the minor technical issues. Although George, if you’re reading this, I’d be willing to trade emails with you about these issues. What really got me started on this was just the whole question of when to learn, and when to outsource. Professional software developers run into this question all the time. There’s even a name for it: The Not Invented Here Syndrome. There’s a great tendency to want to reinvent the wheel all the time. It’s more comfortable to use something you’ve created. I know the feeling, but you can’t create everything yourself and sometimes you’d be better off spending your time some other way.