4 points

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

permalink
report
reply
2 points

Article behind login wall

permalink
report
reply
5 points

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.
permalink
report
parent
reply
1 point

Thanks so much!

permalink
report
parent
reply
1 point
Deleted by creator
permalink
report
reply

Programming

!programming@programming.dev

Create post

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



Community stats

  • 1

    Monthly active users

  • 555

    Posts

  • 2.8K

    Comments