Start learning at 50
Start learning at 50
I've always wanted to learn programming. I've read a blog post saying that at this age it was to late . Then I read a post here in saying the opposite. I've found a site that was learn x in y minutes where it has a bunch of languages there. After reading them, the languages that caught my attention were Julia, Clojure and Go. Are any of these good for a beginner or should I start with something else? I know what are variables, can spot an if/else statement but that's about it. What are some good resources for someone like me who likes to learn by doing things?
You are viewing a single comment
What are you looking to actually do with your programming skills? That will heavily influence which languages to recommend you learn. Do you want to make websites? build games? do AI stuff? Create enterprise-level software? something else?
This is always the question that trips me up.
I'm 5 years younger than OP. I work in a municipal transportation power system job (we maintain and control the grid for trains, trolleys, etc.). I'm sure I'm wasting all sorts of effort in my professional life. I have time. I got a lot out of learning Power Automate. However, if you ask me to pick one specific project, I get overwhelmed because I don't know what's reasonable.
I don't know enough to know if my ideas are achievable, or if I'd just be bashing my head against the wall. I don't know if they're laughably simple tasks, multimillion-dollar propositions, or Goldilocks ideas that would be perfect to learn a coding language.
List out some ideas you're thinking of. While it may not be obvious to you, someone who is seasoned (me or someone else) might notice at least a general theme or idea to point you in the right direction for where you should go and what you should learn, regardless of if the projects are reasonable.
Note - Most projects take teams to realize, so if your ideas are too large, they might not generally be feasible alone.
Feel free to comment some ideas
Achievable is subjective, and even if you progress a ways and learn something that makes you realize that that particular project can't be achieved how you envisioned it, you still have the knowledge to either a) figure out new ways to achieve the same effect, or b) take to a new project.
Knowledge builds on knowledge builds on knowledge. If factor in not starting a project is not knowing enough to know if it's achievable or not, you'll never actually get the necessary knowledge to figure that out. You can't know how to do something until you try to do it...fundamentally.