Self explanatory code

"All your functions and variable names should be self explanatory".

Am I doing it right?

//All names must be self explanatory

selfExplanatory self_explanatory11(selfExplanatory self_explanatory14){
    selfExplanatory self_explanatory7 = SELF_EXPLANATORY1;
    while(self_explanatory14){
        self_explanatory7 *= self_explanatory14;
        self_explanatory14--;
    }
    return self_explanatory7;
}
int main(void) {
    selfExplanatory self_explanatory14 = SELF_EXPLANATORY5;
    self_explanatory14 = self_explanatory11(self_explanatory14);
    printf(SELF_EXPLANATORY2,self_explanatory14);
    return 0;
}

This is top clean code, right? All names in the program are self explanotory!

No magic numbers, either. All constants have a self explanotory name too!

These names are sure better than single letter variable names and put the constants directly in the code, right?

-------------------------------

-------------------------------

--------------------------------

In case you are wondering, this is the result of a code obfuscator I am developing.

It is using the "selfExplanatory" template. The idea is to have several different thematic templates like this.

#coding #programming #software

🚀 LucasMW

Jul 07 · 1 day ago · 👍 CarloMonte · 😄 4

6 Comments ↓

☯️ dragfyre · Jul 07 at 11:36:

still better than Copilot

🦋 CarloMonte · 22 hours ago:

why not randomize the capitalization (i.e. cAMelcASiNg), then put the dash or underscore at random places :-/ ?

🌧️ candycanearter [✍️] · 21 hours ago:

clever i like it :D very malicious compliance

🛰️ lufte · 20 hours ago:

Nice, reminds me of the popular guide to write unmaintainable code.

— https://www.mindprod.com/jgloss/unmain.html

🚀 LucasMW [OP] · 3 hours ago:

Best kind of compliance

🚀 LucasMW [OP] · 3 hours ago:

@lufte. Nice guide. Might take some ideas for my code obfuscator.


Source