At 51, I've noticed there are really two kinds of people at my age... people who are completely beaten, and people who are winning. Once you hit 40 or so, the scope of mortality really hits you. You realize that you've probably already had half your productive life, maybe half a career. You start seeing peers die of "old age" - heart attacks and strokes and stuff. For most, they're beaten, defeated. They decide this…
part of the problem is by the time you're 50, you've had 30 years of adult life to accumulate bad decisions. a lot of people are saddled with obligations they never actually wanted. :(
Learning to code at 56
71–80 of 165 posts
Re: Learning to code at 56
#72This appears to be an Ad for free code camp (not that there's anything wrong with that). Just ten years younger in a similar boat, I'm neither taking a boot camp, nor writing about my "CIS". To each their own. Learning is a life long activity. It shouldn't matter what one learns at any age.
Perhaps it really is an ad, but if it is real, I am impressed that the person thinks at 56, he has enough runway in life to make a serious contribution by coding :-)...I like that attitude.
Re: Learning to code at 56
#73Well, if it is not an ad, at least is some astroturfing, how come the BIG photo is not that of the actual guy? The image on the article is this one: https://i2.wp.com/tobecomeateacher.org/wp-content/uploads/20... "Stock photo" by Jake Barford: https://unsplash.com/@jakebarford The photo of Mr. Vaughn, (from his "profile"): https://cdn-images-1.medium.com/fit/c/100/100/1*Lu4bKAqf2Sxm...
Good find though. This is really fishy.
Re: Learning to code at 56
#74Earlier quoted context omitted.
It does take longer for many people to learn new things when they are 50-60 though. I do think we have to be realistic about the issue that many people who learned and performed complex intellectual skills in their 20s/30s no longer perform this kind of ability to pivot in their 50s/60s; to learn a new craft that depends on learning a lot of new information/skills. Of course this doesn't mean that all people in their…
Speaking as a 43-year old, while I do have some health issues that I didn't have in my 20's, perhaps somewhat surprisingly, I find learning new things as easy as it's ever been. And I honestly don't think I am unusual in that regard. I have a much wider framework of accumulated knowledge than I did 20 years ago, and leveraging that, I can see how wider parts of systems interrelate with a clarity that I never came clo…
New tech is frequently old concepts applied in a new way. Once you recognize those core concepts and can find older analogies, you're way ahead. In the end it's a net gain.
Re: Learning to code at 56
#75I would choose python, ruby(or crystal), c++, c#, etc.. and stay away from the browser, unless you have a very good reason to write for that.
Re: Learning to code at 56
#76At 51, I've noticed there are really two kinds of people at my age... people who are completely beaten, and people who are winning. Once you hit 40 or so, the scope of mortality really hits you. You realize that you've probably already had half your productive life, maybe half a career. You start seeing peers die of "old age" - heart attacks and strokes and stuff. For most, they're beaten, defeated. They decide this…
part of the problem is by the time you're 50, you've had 30 years of adult life to accumulate bad decisions. a lot of people are saddled with obligations they never actually wanted. :(
Re: Learning to code at 56
#77Earlier quoted context omitted.
part of the problem is by the time you're 50, you've had 30 years of adult life to accumulate bad decisions. a lot of people are saddled with obligations they never actually wanted. :(
Life as an adult is fundamentally and naturally about responsebilites and obligations - and most men no longer are able to cope with those because they bought into the illusion of life long youth - aka Peter Pan syndrome.
peter pan syndrome means you never actually did anything with your life (positive or negative), not that you've been beaten down by it. how can you be beaten down by nothing?
Re: Learning to code at 56
#78Well, if it is not an ad, at least is some astroturfing, how come the BIG photo is not that of the actual guy? The image on the article is this one: https://i2.wp.com/tobecomeateacher.org/wp-content/uploads/20... "Stock photo" by Jake Barford: https://unsplash.com/@jakebarford The photo of Mr. Vaughn, (from his "profile"): https://cdn-images-1.medium.com/fit/c/100/100/1*Lu4bKAqf2Sxm...
jaclaz - nice detective work. Photo seemed a little too perfect.
as the image referencing a testimonial "Jordan Blum, EIC, The Bookends Review" whose looks are also slightly different:
http://thebookendsreview.com/about-us/
As a rule of thumb, when it looks too good to be true, it isn't. ;)
Re: Learning to code at 56
#79Please don't go the web developer (javascript) path; node, react, webpack, etc.. It will drive you nuts, things keep changing radically in a very high pace and can take quite some time before you feel comfortable in this crazy field. I would choose python, ruby(or crystal), c++, c#, etc.. and stay away from the browser, unless you have a very good reason to write for that.
Re: Learning to code at 56
#80I submitted this yesterday around Noon and got 3 votes. Today, here it is in another submission. Take a look at the URL. HN apparently uses the entire URL, including hashes, which means this is considered a separate submission. Interesting.
HN is a hit or miss. If you don't get upvoted quickly, you'll get missed. Several weeks ago, 3 of 4 stories that i submitted within two days were completely passed over, only to be resubmitted by other people, which ended up on the front page. One story was even #1 for several hours.
Here it often seems quite random what does get picked up.