this post was submitted on 14 Nov 2023
51 points (93.2% liked)
Programming
17412 readers
73 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Her is my take to try to help you.
If it's your own code, you can add docstrings comments to your functions, so you don't have to re-read the function body everytime. Also, name functions to be understandable more easily when possible.
If not your code, write on a piece of paper (not on computer) the in and out of a function, maybe like so:
Then, you can even connect the functions together and see the whole algorithm:
When projects get more complex, paper will not cut it, then some note taking app of some sort will help. (logseq could help, but some mind mapping or sequence diagram programs would help as well)
Also, I don't know what language your are working with, but learning LISP (maybe clojure) could help.
Why? Because you have to connect your functions together, and it forces you to do so.
At first, it might be harder compared to what you're used to, but it'll give you better fundations to keep learing.