Live data from Hacker News

I didn't learn programming when I was 12

kennyletran.com

61–70 of 85 posts

Re: I didn't learn programming when I was 12

#61
post #60

Starting to program at 18 is early. I took 2 programming courses in college (1 was a Pascal-clone, and the other was an assembly language course), but I essentially taught myself how to program after graduating from college, and have made an entire career out of it, and I'm more than double your age. Don't worry about it, you have plenty of time.

I'm glad to hear that. I'm entering my senior year of Economics and I didn't discover that I enjoyed programming until I took an introductory C++ course last semester. The other day I found myself worrying that I had already missed out on my chance, since I can't currently afford any additional semesters. I'd like to return to study computer science some day, and in the meantime I'm just doing the best I can to learn…

I also studied economics in college, but now program professionally, largely due to my experience at at the Federal Reserve Board of Governors. If you are still looking for work after college, and I assume you are, I recommend you check out their Research Assistant program.

http://federalreserve.gov/careers/ra.htm

For me it was a great way to parlay my economics training into a programming career, even though that wasn't what I was interested in at the time. It's also a great career stepping stone if you're interested in graduate education (not necessarily econ), government work, policy work, law, or myriad other fields. If you want more info, let me know and we can talk offline.

Re: I didn't learn programming when I was 12

#62
post #33
post #22

Earlier quoted context omitted.

what does that have to do with programming may I ask?

That's how you learn programming. I started off editing HTML I copied and pasted from someone and just changing some colors.

While thats where many people start, its worth noting that its really a markup language that lacks core programming concepts (if statements, loops, etc...) Not that it isn't helpful!

And as a relatively amusing anecdote, I started teaching myself HTML when I was 8 or 9, when my family had gotten our first Windows PC. I had no idea what copy/paste was, yet somehow I knew how to view source and ended up handwriting out HTML and then retyping it into Geocities (yep. Geocities). Thats one way to never forget it ;)

Re: I didn't learn programming when I was 12

#63

Starting to program at 18 is early. I took 2 programming courses in college (1 was a Pascal-clone, and the other was an assembly language course), but I essentially taught myself how to program after graduating from college, and have made an entire career out of it, and I'm more than double your age. Don't worry about it, you have plenty of time.

I spent a couple of weeks programming in FORTRAN for an internship when I was 16. I hated it so much that I vowed never to become a programmer. I didn't touch code until about 7 years later. A year later, and I just became a fulltime "Software Engineer" last week! :)

Re: I didn't learn programming when I was 12

#64
As someone who did learn to program at the age of 12 (and is now 32) I don't think it matters. Programming is not that hard to learn - it's another language that is far more straightforward than trying to learn a spoken language that might have genderizations, weird grammar rules and so forth. The actual learning to program is not complicated.

What is complicated, is the analytical mindset that makes a good programmer. I believe that the better programmers just have this mindset and it is what makes them good at what they do. Coupled with a passion for the technology they are using, this will make them better at what they are doing regardless if they have 2 months behind them, or 20 years behind them - and also regardless of the age they start at.

Re: I didn't learn programming when I was 12

#67
post #16

I'd say programming is like architecture. Most architects don't start learning their craft until age 20+. Yet those "late bloomers" still go on to do amazing things. If it was as easy to learn architecture as programming, we'd probably see blogs from people wondering if age 18 is too late to start doing architecture.

But most architecticts were artistic sketchers at a youndlge age. For programming, something like math or logic or Latin would br analogous.

Re: I didn't learn programming when I was 12

#68
post #48

Programming is not a race with one winner. There are a ton of programmers making 6 figures, and the distribution of possible incomes for someone who can program and ... has no real upper bound. You are very unlikely to be the second coming of John Carmack, but you can still have a plenty good life. Welcome aboard, start your learning curve, and keep it going. There is only one big tip that I have. A level people like…

I agree with this, however I do feel compelled to expand upon it.

A level types really only like to hang around A level types. Being a B or C player in a room full of high achievers can at times be downright (if not outright) unpleasant.

If I had my druthers, I'd choose to be the 2nd dumbest person in a given room. Being an order of magnitude or two behind the mean is more demotivating than educational.

Re: I didn't learn programming when I was 12

#69
post #61
post #60

Earlier quoted context omitted.

I'm glad to hear that. I'm entering my senior year of Economics and I didn't discover that I enjoyed programming until I took an introductory C++ course last semester. The other day I found myself worrying that I had already missed out on my chance, since I can't currently afford any additional semesters. I'd like to return to study computer science some day, and in the meantime I'm just doing the best I can to learn…

I also studied economics in college, but now program professionally, largely due to my experience at at the Federal Reserve Board of Governors. If you are still looking for work after college, and I assume you are, I recommend you check out their Research Assistant program. http://federalreserve.gov/careers/ra.htm For me it was a great way to parlay my economics training into a programming career, even though that wa…

Thank you. I imagine such a position would be very competitive.

I'd definitely be interested in hearing more about your application process, how prepared you felt you were based on coursework, and of course what the job was actually like.

Re: I didn't learn programming when I was 12

#70
post #56

People are already telling you that eighteen is not too old to learn programming. And they are correct. People start at forty and fifty. I have a different point to make. There will always be someone smarter than you. Someone who started younger, learned faster, accomplished more. They're smarter than you are now, and they'll probably always be smarter than you. Just get used to that as quickly as possible and move o…

Excellent post. I read every word. I would go even further. Even though you state that for any person member of humans, there exists someone smarter than person, sometimes you slip into writing as if there is a linear ordering. The geniuses and prodigies, sure if you project unto one dimension you can find a few people who dominate. Maybe you can find a few such dimensions. But there are vastly more dimensions where…

I agree that linear ordering is a fallacy. But the fact that I kept slipping into it is probably deliberate, if often subconscious.

Part of that is just to make it flow better: The art of explanation is to choose one clear line of pursuit and gloss over the complications. But I think there's a more important reason: The real world is multidimensional, but feelings of inadequacy are not. When I'm feeling good about myself I can recognize that there is no one true scale on which two people can be compared. But when I'm depressed and I think about smart people I just see a bunch of folks who are "more talented".

Depression messes with one's mind, to snap oneself out of it is not always possible (save your life, see a counselor) and when it's possible the mental trick that is required is different for everyone. The "by which arbitrary yardstick?" gambit is one such trick. My essay above is an expression of a different gambit.

(In other words, my rhetorical characterization of the various arguments as "weak" and "strong" versions of a single argument is also a false linear ordering. ;) Oh, the things we do for rhetoric.)

Post reply on HN