The candidate had been referred by a friend of mine who offered the personal bio ahead of time, probably to filter out any polite but intolerant employers. Before the interview started I forcefully reminded myself to keep an open mind and conduct the interview as I would any other.
Half way through the interview it sort of suddenly dawned on me that I really didn't care, at all, about this person's personal orientation, preferences or lifestyle; as long as they could code, I would be happy to have them on board (as a co-worker and friend, as co-workers tend to become in such close quarters). And I felt intuitively confident that my co-founder would feel the same way. A lot of folks probably repeat this sentiment every day, but I wonder in how many industries they really, truly mean it. I think tech is a very special industry in terms of its ability to focus on substance, as you say, over form or perception.
When you try to get on the hype train, ageism is prevalent, but that's been as true of music and fashion for many decades as it is for network-related businesses.
I also had the pleasure of showing how I could get better, more accurate designs by doing some FORTRAN programming as opposed to the older manual methods.
I think having old mixed with young, the new techniques and the old techniques, made for having a great team.
It's actually quite critical. The oldbies have learned things that were completely phased out of the newbies' curriculum. A few years ago my dad mentored university seniors working at their senior project; one of the things he complained about was that they were not taught how to machine a part. As a result they had little gut-level knowledge about details like tolerances. Since a mechanincal engineer's work output is instructions for a machinist, learning how the machinist does his job is essential to you doing yours, even if you spend next to no time on the job at a lathe or mill.