So he helped us get off the ground with some new-to-us tech we were using, but it turned out that his Ruby code pretty much sucked. So maybe Ruby's not really his thing. He was supposed to be writing about PHP at that publication, so I looked up his articles. Not a single one with even a line of code. Just unfulfilled future plans and occasional business/culture musings. And really the problems with the Ruby code weren't just syntax or library unfamiliarity--there were smells there that should have been bothersome in any language.
So I start filing bugs against his code, and it turns out he's not interested in fixing them. In fact, if the startup has any more "architectural" consulting they want him to do, he'd be happy to weigh in, but he doesn't really like to code much anymore.
Yeah--my respect for him as a developer went way, way down. (I'm not comfortable saying respect generally here.)