Bruno and canuck, thanks for the interesting insights. I'm taking notes.

Quote:
I want to see a completed project, not a routine...

Since a developer is likely a part of a larger team, I'd have to see the project they contributed to and examine their part of it.

Another idea is to interview them and ask them how they'd solve specific problems. It'd be hard to rip off the Internet during an interview, and would show their higher level thinking. To me, syntax is far less important than the actual problem solving.

Quote:
to go to a small "shop" or "studio"

Thanks, I didn't know development shops would create apps designed by a client. That may be the way to go. It has some of the same downsides (they're the only ones who can maintain the code) and some new ones (my work will be fit in among their other clients).

Thanks again.
_________________________
-
FireFox31
110gig MKIIa (30+80), Eutronix lights, 32 meg stacked RAM, Filener orange gel lens, Greenlights Lit Buttons green set