this post was submitted on 06 Aug 2024
42 points (97.7% liked)

Learn Programming

1634 readers
8 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 1 year ago
MODERATORS
Ategon
JaumeI
bugsmith
42
How to go from writing code that works to writing efficient, clean code and following good practices? (self.learn_programming)
submitted 2 months ago* (last edited 2 months ago) by andioop to c/learn_programming
27 comments fedilink hide all child comments
 

Besides some of the very, very obvious (don't copy/paste 100 lines of code, make it a function! Write comments for your future self who has forgotten this codebase 3 years from now!), I'm not sure how to write clean, efficient code that follows good practices.

In other words, I'm always privating my repos because I'm not sure if I'm doing some horrible beginner inefficiency/bad practice where I should be embarrassed for having written it, let alone for letting other people see it. Aside from https://refactoring.guru, where should I be learning and what should I be learning?

you are viewing a single comment's thread
view the rest of the comments
[–] RonSijm 3 points 2 months ago

I’m always privating my repos because I’m not sure if I’m doing some horrible beginner inefficiency/bad practice where I should be embarrassed for having written it, let alone for letting other people see it.

Well that's something not to do. Make you "horrible code" public, and ask people to do a code review. Or see what contributors want to change through a PR (if you're so lucky). You're not going to learn anything from others by hiding your mistakes. And no one besides you really cares if you're committing horrible code.

It's pretty hard to just give generic advice on how to write clean code, but if people can just tell specifically what you can improve it's much easier