Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@endre86 That was my first thought, but then I realised that I do it when debugging sometimes.
-
endre862238y@lreading But I bet they still mean something. A response from something, a partial calculation, etc. If it's just for debugging, sure you don't want to use time finding a suiting name. But sometimes I find that the debugging variable is nice to keep in the code, because there happened something that was not transparent.
-
I don't declare variables without meaning and if you do you should be ashamed.
-
@oskaremil I bet your shit doesn't stink either, and you've never had trouble debugging something.
-
thing, shit, test, one, two.. But those are just some placeholders (until you find the meaning).. all variables have meaning.. if they don't, they don't belong.
-
All variables should have meaning.
If you are talking about iterators, something like i.
If you're talking about callback function arguments that never get used, I still name them according to what they represent, even if they don't ever get used. -
basior4908yIn my country (Poland), the most common is "dupa", as a temporary variable for everything. But you'd better never forget to remove it before outage or presentation.
!rant
What do you name variables with no meaning
undefined