Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Learning to code at 56

medium.freecodecamp.com

Post reply on HN
Print view View original

11–20 of 165 posts

Re: Learning to code at 56

#11

Post by Baeocystin »

johansch wrote: post #7
hd4 wrote: post #5

As long as you still have a working memory, you can learn anything at any age, I don't go along with this 'old-dog-can't-learn-new-tricks' thinking. Though obviously when you're younger it's markedly easier to pick up a new skill.

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 close to touching in my youth.

Perhaps this too will fade in another 20 years, but so far I'm actually enjoying having a middle-aged mind. I can accomplish so much more than I could before.

Re: Learning to code at 56

#12

Post by BatFastard »

Baeocystin wrote: post #11
johansch wrote: post #7

Earlier 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…

As a person in the 50-60 year range, I can say that learning new things is a mixed bag for me. When I was young I was like Velcro, throw information at me and it stuck. Now only the important information stays with me. I wish I could have learned that in my twenties. I would not have a head full of useless information...

One advantage of being older is I tend to have a more seasoned perspective of what's important and whats not important in the long run.

Re: Learning to code at 56

#13

Post by kbart »

counterplex wrote: post #10
superplussed wrote: post #9

Obviously things are going to be tough as a 50s junior developer, but it sounds like you are up for the challenge. And hey, we all have to do something with the time we are here. It might as well be something you enjoy, challenges be damned.

I'd imagine by your 50s you'd have already learned the right attitude to succeed at anything: do the best you can, ask for help often and speak up right away when scope explodes! This makes things easier, not more difficult.

Attitude is not the problem here, getting a job is. Few acquaintances of mine in their thirties also try to jump this developer bandwagon and it's very hard to get a junior position for them, because they are "too old" (of course, nobody says that directly). Actually, they started to get interviews only after had hidden years in their CVs (as per mine advice).

Re: Learning to code at 56

#14

Post by pc86 »

BatFastard wrote: post #12
Baeocystin wrote: post #11

Earlier quoted context omitted.

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…

As a person in the 50-60 year range, I can say that learning new things is a mixed bag for me. When I was young I was like Velcro, throw information at me and it stuck. Now only the important information stays with me. I wish I could have learned that in my twenties. I would not have a head full of useless information... One advantage of being older is I tend to have a more seasoned perspective of what's important an…

Whose definition of important? :)

Re: Learning to code at 56

#15

Post by tonyedgecombe »

kbart wrote: post #13
counterplex wrote: post #10

Earlier quoted context omitted.

I'd imagine by your 50s you'd have already learned the right attitude to succeed at anything: do the best you can, ask for help often and speak up right away when scope explodes! This makes things easier, not more difficult.

Attitude is not the problem here, getting a job is. Few acquaintances of mine in their thirties also try to jump this developer bandwagon and it's very hard to get a junior position for them, because they are "too old" (of course, nobody says that directly). Actually, they started to get interviews only after had hidden years in their CVs (as per mine advice).

Which is quite funny when you consider many of us are using technology that is only a few years old and we are constantly told we shouldn't stop learning to have a career in programming.

Re: Learning to code at 56

#16

Post by weakeyesforit »

At my age the main problem is that I read a lot in a computer screen and my eyes get tired. Recently I read in the last weak several books for learning Erlang and Elixir and one for refreshing ruby. Last month I learned java by doing several projects with netbeans. Initially I programmwd only with gedit and googling stack overflow. I was programming feom six pm to five am to help my son with a java project. Honestly helping him is not doing any good but not helping is not any better. Were my eyes and health stronger I think I could learng anything in little time. I learned the hard way failing one and again. You couldn't believe that I stumpled with all the walls before continuing along, bit what don't kill you make you stronger. Get ready for the next battle, we will win.

Re: Learning to code at 56

#18

Post by treehau5 »

weakeyesforit wrote: post #16

At my age the main problem is that I read a lot in a computer screen and my eyes get tired. Recently I read in the last weak several books for learning Erlang and Elixir and one for refreshing ruby. Last month I learned java by doing several projects with netbeans. Initially I programmwd only with gedit and googling stack overflow. I was programming feom six pm to five am to help my son with a java project. Honestly…

Have you tried flux? https://justgetflux.com/

It helps me with the eye strain. Also I am starting to find myself returning to good ole paperback books for reading. Try printing out some code bases when ever you start getting more advanced you can actually learn a lot from studying code.

Re: Learning to code at 56

#19

Post by BatFastard »

pc86 wrote: post #14
BatFastard wrote: post #12

Earlier quoted context omitted.

As a person in the 50-60 year range, I can say that learning new things is a mixed bag for me. When I was young I was like Velcro, throw information at me and it stuck. Now only the important information stays with me. I wish I could have learned that in my twenties. I would not have a head full of useless information... One advantage of being older is I tend to have a more seasoned perspective of what's important an…

Whose definition of important? :)

Everyone has their own definition of important. I would like to think that after writing software for 30 years I have a decent knowledge of what my customers value.

So for me, reliability, scalability, and ease of use are more important than whether a language supports tail recursion and dynamic typing.

Re: Learning to code at 56

#20

Post by nkristoffersen »

treehau5 wrote: post #18
weakeyesforit wrote: post #16

At my age the main problem is that I read a lot in a computer screen and my eyes get tired. Recently I read in the last weak several books for learning Erlang and Elixir and one for refreshing ruby. Last month I learned java by doing several projects with netbeans. Initially I programmwd only with gedit and googling stack overflow. I was programming feom six pm to five am to help my son with a java project. Honestly…

Have you tried flux? https://justgetflux.com/ It helps me with the eye strain. Also I am starting to find myself returning to good ole paperback books for reading. Try printing out some code bases when ever you start getting more advanced you can actually learn a lot from studying code.

I'm always preaching the holy word of flux to everyone I meet. Even family members who don't code :-)
Post reply on HN