Asklemmy

43885 readers

1872 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

How did you get into coding/programming? (sh.itjust.works)

submitted 4 months ago* (last edited 4 months ago) by gnutard@sh.itjust.works to c/asklemmy@lemmy.ml

39 comments fedilink hide all child comments

I've always had trouble getting into coding/programming because I've never truly dedicated myself to it. Mostly, this is because I kinda always lose momentum to learn it. I'm a heavy FOSS user; I love coreboot/Libreboot and am interested in getting into firmware development. I've already helped test hardware for Libreboot and enjoy learning about firmware.

I have just started to cut out gaming from my life to focus more on this. Maybe I should start with Python? At the same time, though, I feel like I should start with C, but don't want to jump the gun too quick.

Feel free to share your stories!

you are viewing a single comment's thread
view the rest of the comments

[–] reversebananimals@lemmy.world 12 points 4 months ago

I was a self taught programmer who 10+ years later is now a senior software engineer. I can't tell you what to do but I can tell you what worked for me.

The reality is, I never sat down with the intent to "learn programming". Instead, I had practical ideas for things I wanted to make the computer do, and then I learned whatever was necessary to accomplish my projects as I went. Whenever I got stuck or hit an error, I'd search my questions online.

I never truly "finished" most of these early projects but they gave me a practical understanding of how things fit together. From there I just kept making stuff and taking on harder projects and then harder jobs and eventually other programmers started coming to me asking for help because they knew I had solved the thing they were working on before.

I'm not sure if it's advice, but I'd say stop worrying about learning and just do. If you like firmware, go buy some shitty unsupported peripheral from Goodwill and try to make it work on your modern system. Solve a problem you have in your everyday life. It doesn't matter if you accomplish the goal, you'll learn a lot by googling your way through it. Do that enough and you'll wake up one day and be a competent programmer.