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.
Programmer Humor
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
"Hmmmm. This codebase seems surprisingly lightweight."
Opens random 'Helper' class.
"Oh... Oh boy."
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.
Haskell also tends to have really small main functions, since the functional paradigm encourages splitting it up
main : IO ()
main = test allTests
No OOP in sight: https://gitlab.com/bss03/grtt/-/blob/f760eb6f0c1f1b171a1a3a114e156f008e4227d0/grtt-machine/test/src/Main.idr
It's a beautiful feeling when everything is nicely encapsulated.
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.
You should post the code!
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.
Is it normal to need an account to view code on GitLab?
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
Unfortunately, yes
Then sadly, the code shall remain a mystery for me.
See my other edited comment.
Script? Not library?
In my case it was a script, but for libraries this would hold true too.
"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.
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.
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. 🥴
i have been summoned
How it should be.