Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I know you've heard it, but seriously, the biggedst hurdle to learning programming is having a solution looking for a problem. You can learn all kinds of stuff in the abstract, but your brain will either handwave over it or bounce off, if it can't contextualise the knowledge into a problem-solving tool.
A source of small but genuine needs is the scarcest resource.
I know the world has moved on to big cosy high-level languages that let you think semantically about everything but honestly I'm still a big fan of starting with C; it is something of an austere discipline, but it gives you a boots-on-the-ground view of the problems you're working with, and I think that really helps shape your understanding of what you're dealing with.
(you could do a fair bit worse than the game 'human resource machine' for a slightly gentler introduction, then pick up some exercises in C, then move to python or similar - it will let you appreciate the cosy high-level stuff, and have a better feel for why you're doing stuff)
My only real exposure to coding is C in Turbo C++ it was not a nice surprise when I later looked at other IDEs and was not sure where to begin. Maybe I’ll just get started with Turbo again lol.
aw hell yeah, that ruled back in the day.
Might be challenging to get it running in a modern environment, but I admire your taste in the classics :)