It's just math, really.
It's just math, really.
Even though this thread sounds like "Why don't I get hired?" that's not what he actually asked.
To make a more general point, you need balance, at least as soon as you can afford it. You don't necessarily need to make an experienced programmer a lead, but you ought to listen to him when he says "If once you start down the dark path, forever will it dominate your destiny, consume you it will..." (i.e. help you see how much technical debt it will incur).
And then there are the things that just won't work at all: you don't need an experienced per se programmer, but you're likely to be very unhappy if you don't have one who knows big O notation and regularly does the math, so you aren't e.g. trying to get 100x or more the max peak transaction rate out of your database, exceed the bandwidth of your systems, etc.
Another I noticed after programming C/C++ for more than decade was an ability to hone in on many bugs in seconds/minutes where the less experienced could take hours/days. How do you value that type of "productivity"?
And those are now the guys with 10+ years of experience.
> How do you value that type of "productivity"?
There's also the productivity of not using C/C++.
I just generally find this discussion interesting, since I'm a 'recent graduate' with 10+ years of experience...
Absolutely. But now's different... and someone who's
programmed in C since the 90s is going to be really upset
when they sign up for a startup and they're coding in Ruby.
For the sake of argument, let's assume that "Ruby" in that sentence is a proxy for any of the "newish" langauges that are out there. If we can go with that assumption...Well, let' see; as somebody who started programming in the 90's with C and C++, I would say that your assertion is simply not true. Maybe some people are dinosaurs and don't change with the times, but I made the switch from (primarily) C/C++ to (primarily) Java about 2002, and started dabbling in Erlang and Ruby about 2008, and am doing a lot of work in Groovy now, while spending some time learning Scala and Clojure.
(Speaking of which, there's a TriJVM Hack Night tonight, for anybody in the RTP area! http://www.meetup.com/TriJVM/calendar/13771811/ )
And I've written some Python and Ruby as well. So no - based on my experience (and observations of colleagues about my age) I don't think it holds that somebody who was doing C/C++ in the 90's is necessarily a fossil who won't be interested in doing Ruby (or whatever).
To be fair though, I was just starting in programming in the 90's, so I may be younger than whatever stereotypical character you had in mind by saying that. <shrug /> I still think it's dangerous to generalize in this fashion though.
However I'm guessing the assumption that they can't might be another reason why 23 year old startup founders are loath to hire them.
But see my comment here: http://news.ycombinator.com/item?id=1439535
But all generalizations are still false.
Also, hardly anyone in startupland is married with kids by age 30.
And, nobody with a professional job in any capacity (programmer, doctor, lawyer) leaves work at 5pm.