[deleted]

Comments

• Kache@lemm.ee ⁨11⁩ ⁨months⁩ ago

  Just the commonly repeated mediocre rules-of-thumb-you-should-follow (but not always) stuff.

  source
• RagnarokOnline@reddthat.com ⁨11⁩ ⁨months⁩ ago

  Article behind login wall

  source

  • blackbarn@lemm.ee ⁨11⁩ ⁨months⁩ ago

    Wasn’t for me. However here are some key moments:

    Follow the principles of object-oriented programming like inheritance, encapsulation, and polymorphism.
    Don't overuse inheritance - the relationship between classes should make logical sense.
    Keep methods short - if a method exceeds 50 lines, look for ways to abstract functionality out.
    Consider existing open-source solutions before writing your own code from scratch. Leveraging others' work saves time.
    Avoid hacking together quick fixes - take time to implement proper, maintainable solutions.
    Plan for reusability - code with the goal of making parts reusable by yourself and others.
    Prioritize readability - write code that's easy for others to understand.
    Modularize your code into logical, independent pieces.
    Test early and often to catch bugs quickly.
    Refactor regularly to improve design as your understanding evolves.
    

    source

    • RagnarokOnline@reddthat.com ⁨11⁩ ⁨months⁩ ago

      Thanks so much!

      source