Nah, always use as lewd names as possible, like really over the top, preferably r34 compliant. And the comments need to be there to explain the fictional stories behind all the names and all the lewdness - and not really to explain what the code does, that’s just a common misconception.
If someones dares to look into my code they need to be ready to suffer.
(And no, I’m not a dev, no one in my team can code anything, boss won’t give me a an actual dev - and when I write something for other ppl as a favor I make an effort to make the code clean and comments only mildly amusing)
Reminds me when back in the day I was working on a system where one of major component’s acronym was BOOTY. It was hard picking right terms and names for the new parts, but I managed to fit a variable named BOOTY_SLAP in there such that none of the reviewers even questioned it.
Nah, always use as lewd names as possible, like really over the top, preferably r34 compliant. And the comments need to be there to explain the fictional stories behind all the names and all the lewdness - and not really to explain what the code does, that’s just a common misconception.
If someones dares to look into my code they need to be ready to suffer.
(And no, I’m not a dev, no one in my team can code anything, boss won’t give me a an actual dev - and when I write something for other ppl as a favor I make an effort to make the code clean and comments only mildly amusing)
Reminds me when back in the day I was working on a system where one of major component’s acronym was BOOTY. It was hard picking right terms and names for the new parts, but I managed to fit a variable named BOOTY_SLAP in there such that none of the reviewers even questioned it.
Quality work!