It was literally like that. I had a script of about 310 lines and the main function was like 10-20 lines of code. I had a very nice Setup of objects that handled all functionality possible behaviours independent and so my main function was just receiving a user input from another function and add accordingly which included like 3-4 different scenarios that are being handled in the main function.
OOP for the win
21 Comments
lwhjp@piefed.blahaj.zone · 40 pts · 208d
It's a beautiful feeling when everything is nicely encapsulated.
cows_are_underrated@feddit.org · 8 pts · 208d
Its also very nice, when you spend hours writing everything else and then once all of it has been tested you write a few lines of code in the main function and 10 minutes later everything works as it should.
jubilationtcornpone@sh.itjust.works · 24 pts · 208d
"Hmmmm. This codebase seems surprisingly lightweight."
Opens random 'Helper' class.
"Oh... Oh boy."
kryptonianCodeMonkey@lemmy.world · 23 pts · 208d
I mean... that is just good design. The main function should be the initializer and orchestrator of the logic. You should be able to look at the main function and tell, at a high level, what the program is doing. It should be usually pretty basic and procedural. Other functions handle the details and complexity.
Ephera@lemmy.ml · 14 pts · 208d
Yeah, always found that weird as a junior. I basically never touched the main-function, because well, it set up some fundamentals and then called some other function or created some objects and then I was tweaking things somewhere below that.
Now that I'm a senior and taking over the lead of projects, I'm the person that touches the main-function and others generally do not. 🥴
bitcrafter@programming.dev · 7 pts · 208d
Just be wary of writing ravioli code which forces the person reading your script to have to constantly jump around it in order to figure out what is actually going on.
deadbeef79000@lemmy.nz · 7 pts · 208d
"My Script" should be another dozen books the same thickness as main.
Not, I stress, for the sake of it, but for proper implementation of the suitable patterns for the application.
cows_are_underrated@feddit.org · 5 pts · 208d
Well, it was really just a script that has exact one purpose. I just split it up beautifully, so that my main function is very short.
bss03@infosec.pub · 6 pts · 208d
No OOP in sight: https://gitlab.com/bss03/grtt/-/blob/f760eb6f0c1f1b171a1a3a114e156f008e4227d0/grtt-machine/test/src/Main.idr
bleistift2@sopuli.xyz · 1 pts · 208d
MonkderVierte@lemmy.zip · 5 pts · 208d
Script? Not library?
cows_are_underrated@feddit.org · 3 pts · 208d
In my case it was a script, but for libraries this would hold true too.
KSPAtlas@sopuli.xyz · 5 pts · 208d
Haskell also tends to have really small main functions, since the functional paradigm encourages splitting it up
victorz@lemmy.world · 4 pts · 208d
How it should be.
andioop@programming.dev · 4 pts · 208d
i have been summoned
seadoo@lemmy.world · 3 pts · 208d
You should post the code!
cows_are_underrated@feddit.org · 4 pts · 208d
Here you go: https://gitlab.com/foss9293204/southpark-downloader
Keep in mind, this is in production code that works in a testing environment, but is not ready yet. Theres also almost no documentation.
bitcrafter@programming.dev · 4 pts · 208d
Is it normal to need an account to view code on GitLab?
mnemonicmonkeys@sh.itjust.works · 3 pts · 208d
Unfortunately, yes
bitcrafter@programming.dev · 1 pts · 208d
Then sadly, the code shall remain a mystery for me.
cows_are_underrated@feddit.org · 2 pts · 208d
See my other edited comment.
cows_are_underrated@feddit.org · 2 pts · 208d
Idk, this is the first time I used gitlab in private (i literally just set up my personal gitlab account for this, since pastebin complained about some parts of the code).
Edit: It should be publically visible now: https://gitlab.com/Aipathon/southpark-downloader