59
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Feb 2024
59 points (98.4% liked)
Programming
17207 readers
288 users here now
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
founded 1 year ago
MODERATORS
Too often, you won't be given time to make your software understandable. Probably almost never. So you have to incorporate a way of programming that leaves your code more understandable after you fixed your bug or added your feature.
I don't know if understandability is the most important thing. However I certainly agree with the author that it's curcial, if you ever want to do more than merley a script or a proof of concept.
So write it properly from the get-go. You can get 90% of the way by naming things properly and following the Single Responsibility Principle.