Asklemmy

43936 readers

440 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
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

How did you get into coding/programming? (self.asklemmy)

submitted 4 months ago* (last edited 4 months ago) by gnutard to c/[email protected]

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

[–] [email protected] 3 points 4 months ago* (last edited 4 months ago)

I had my start with Python, albeit as a kid and I didn't actually understand too much about the principles at the time. Still, I think that was a good place to start learning about the concepts of instructions and variables.

I learned more about the ideas underpinning it all later, and most of my understanding came when actually working in software development on a live and in-development codebase. I think that's a good progression: start small, then learn some theory just so you've heard the terms once, then try to make sense of actual code using that.

Edit: definitely work on some goal though. Don't code in a vacuum, think of something small you want to achieve and learn to do that.