this post was submitted on 12 Feb 2026
59 points (100.0% liked)

Learn Programming

2086 readers
50 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. 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
 

I don't need something practical. I just need something fun to keep me motivated.

you are viewing a single comment's thread
view the rest of the comments
[–] ageedizzle@piefed.ca 4 points 3 days ago (1 children)

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?

[–] nate3d@lemmy.world 3 points 3 days ago (1 children)

Anti-patterns are essentially what ‘not to do’. Heres a good series of Medium articles on it!

[–] ageedizzle@piefed.ca 4 points 3 days ago (1 children)

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!

[–] orclev@lemmy.world 2 points 3 days ago (1 children)

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).

[–] ageedizzle@piefed.ca 1 points 2 days ago

Haha nice. I'll keep my nose out for any funky code smells. Thanks!