Programming

17424 readers

68 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

150

Start learning at 50 (lemmy.world)

submitted 6 months ago by Agualusa@lemmy.world to c/programming@programming.dev

57 comments fedilink hide all child comments

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's thread
view the rest of the comments

[–] Adderbox76@lemmy.ca 3 points 6 months ago* (last edited 6 months ago)

I don’t know enough to know if my ideas are achievable, or if I’d just be bashing my head against the wall.

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.