this post was submitted on 12 Feb 2026
59 points (100.0% liked)
Learn Programming
2086 readers
50 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Python is one of the more forgiving and extremely versatile.
I highly recommend checking out the game “The Farmer Was Replaced” on Steam as it might be the best way to introduce yourself to programming concepts outside of a classroom. (Not affiliated, just love the game XD)
Then in no particular order:
And as always - learning the anti patterns is more important than learning the patterns.
Hey thanks for the game recommendation. It's always nice to have some leisurely activity that is fun to do but you can feel productive doing anyway. Thanks for the language list too.
This might be a basic question but what do you mean exactly about 'learning the anti-patterns'? Can you expand on that?
Anti-patterns are essentially what ‘not to do’. Heres a good series of Medium articles on it!
Interesting! This feels like it's going to be something that, once you understand it, you can't believe you ever programmed without it. Thanks!
See also the closely related concept of code smells. These are things that aren't necessarily wrong like anti-patterns are because in certain niche cases or in limited amounts they're fine, but they're often an indicator that you're doing something wrong in your code. As a quick example I looked up some code smells in JS and a couple of the examples were using
==instead of===and having deeply nested/indented code (E.G. have if blocks inside of if blocks inside of if blocks inside of a for loop).Haha nice. I'll keep my nose out for any funky code smells. Thanks!