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?

  • Windex007@lemmy.world
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    3 months ago

    I think this is the kind of advice that if taken without context as a dogmatic approach, you’ll get worse code.

    There are ideas around “exit early” and “balanced branches”… But they’re IMO a pretty low-value add, and the likelihood of misapplication is pretty high.

    I’d be way more focused on designing for testibility.

    If you focus on that, so many good design choices will fall out naturally.