4 ms·
Starting early is not a requisite for success. I started programming when I was 19 or 20 (not that I'm necessarily a successful founder but I have found some me
by delano 16y ago
Starting early is not a requisite for success. I started programming when I was 19 or 20 (not that I'm necessarily a successful founder but I have found some measure of success during my IT career).
Your knowledge in various domains likely helps you in ways that aren't immediately apparent. (Team sports, for example, are great for health but also for social skills.)
- johnrob 16y agoStarting early certainly isn't a requisite, but it can be a pretty big advantage in most fields.
- nostrademons 16y agoThe big advantage is that you can get to your mid-20s with 10 years of experience and lots of practice, and then be mentally ready without having the commitments of a house, wife, kids, mortgage, etc. tying you down. You can get those same advantages by delaying dating & childbirth until later in life, although then you sacrifice in that your kids may never know their grandparents.
- timr 16y agoWhen it comes to software, I don't think starting age matters that much, except perhaps on the margins. The field changes too quickly for amateur technical experience from 10+ years ago to have much of an impact on quality. The kind of experience that ages well is the kind that you can't easily get as a teenager with a Linux install. Also, every time I interview someone, I ask them how they got into programming. So far, there's been no strong correlation between quality and years of experience. The people who started programming in elementary school are just as likely to be crappy as those who didn't start until college. The strongest predictor I've seen for engineer quality is college GPA. People who work hard and get things done also tend to get good grades.