Hacker News new | ask | show | jobs
by fatalogic 3407 days ago
I think it doesn't really matter. Programming is not a physical impossibility for a vast majority of people. Like I could train for years and never be able to bench press 400lb because of genetic limitation but learning to program doesn't have that limitation. Learning to program like most skills just takes time, effort and dedication. I think if you fail at it either you weren't as interested as you thought or you may have been trying to learn a language that just didn't vibe with you.

Programming also seems like the only profession people just assume they can pick up in a year. No one wakes up and says I'm going to quit my job and become a doctor, or a professor, or lawyer in 3 months to a year. If they are making that type of career switch they go in with the expectation that they will have a lot to learn and it is going to take more than a year of concerted effort. Not everyone is going to become a software engineer at google or apple but there are plenty of well paying programming jobs.

Sorry for the long post I just get frustrated when people want to look at others failures as a gage for their own capabilities. Believe in yourself and put in the work, the results will come.

“He who who says he can and he who says he can't are both usually right” – Confucius

2 comments

I see your point, but I think you may have missed mine. Let's say there are ten successful older programmers interviewed. Seven of them went to coding basecamps, two of them went back to school, and one of them was entirely self-taught. I, as someone who wants to be a developer concludes that going to a coding boot camp is the best way to become a developer later in life.

The problem is that there might be 1000 people who attended boot camps and went on to work in McDonalds for every one who got a developer job — 0.1 percent became developers. But maybe only ten of the self-taught people work in McDonalds for every one who got a programming job. It would be smarter to self-learn in that situation.

But, if all you ever see are the successes, you have no way to decide which is the best course of action.

I don't think that's true at all. I suspect many people don't have the obsessiveness, attention-to-detail, memory, and perseverance that a programmer needs to fix a hard bug. And not many people would enjoy a job that requires sitting motionless in front of a computer for long hours. (I love it, though!)