• 0 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle















  • My first computer was an Oric-1, and I typed a little bit of BASIC on it, and even managed to save to a cassette tape! (never managed to reload what I saved though lol) This first computer was traded to me by a friend for I don’t remember what, but it made me interrested into computers for sure!

    Next, with that same friend, I traded again and got an Atari 520 STE, that’s where the story really begins! I was about 14 at the time. Since then, I stopped leaving my room, and started to read a 500+ pages book about GFA basic. I have so good memories about the things I could do with that computer, even to nowadays standards, it’s the best computer ever! I remember I had a 30Mb hard drive in SCSI, and some accessories. It’s still at my parent’s house. I miss it.



  • 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:

     [1,2,3] -> (sum function) -> 6
    

    Then, you can even connect the functions together and see the whole algorithm:

    [1,2,3] -> (sum) -> (multiplyBy2) -> (...) -> final_result
    

    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.