Dune is exactly what Lucas was copying when he wrote Star wars.

Any mention of a server room reminds me of the fable of the guy, we'll call him Mike, who unplugged the Internet.

I can't remember where I read it, I think it was greentext on Reddit years ago.

So Mike is an intern, and due to some weird circumstances he becomes the only network admin in the building. Well, one day he doesn't esnt feel like working, so on his way in, he stops by the server room and unplugs the internet.

He then goes to his desk like a normal day. Then he starts getting phone calls. Everybody is freaking out because there is no Internet. So he begrudgingly descends into the server room and starts playing video games on his phone.

Close to the end of the day, he plugs the Internet back in and ascends a hero to the employees because they think he's been working hard all day to give them internet.

I'm poor too friend. I just prefer to spend my time differently. And I think that's ok.

No, it's more like I think the oligarchical media is controlling a lot of this thought, and I refuse to subscribe to the conditioning.

I appreciate your emacs perspective, thanks for the input.

I get the sense that programmerhumor hates prefixes, but I'm telling you, they have changed my life. Next project-for-fun, just give it a try and see what happens. I think you'll be surprised.

To many of your points, I say I agree that a lot of naming conventions depend on context. The environment you're working in, the IDE, the team you're working on, the language you're coding in.

However, prefixes I'm firm on. I think it's unpopular because it's from a bygone era where IDEs were non-existent. And while yes, ides have replaced many of the uses, they have been the most radical change to my readability and comprehension of the code I've written.

Also, I'm mostly a js programmer, so yes, very different from emacs.

Also, for calc_SumYears, I literally meant to add the years together, hense the prefix. So, maybe the prefixes are a little more useful than you give them credit.

I have to disagree on some points, but I def feel like you're helping me learn, so for that I am grateful.

I feel like you're speaking from the perspective of a perfect coding environment, which if you have that, that's great. Maybe all your code is in one place, maybe you have an IDE that does a lot of the work for you, and that's great. However, for most of us, that's rarely the case.

Prefixes have been an absolute game changer for me personally, and I will never not use them again.

I have also found that verbosity of variable name and readability are mutually exclusive. A long variable name, most of the time, takes away from the logic. Yes, they are "free" as far as memory, but are very expensive to reliability.

Units tests, again are great, but most places think unit tests are like golden toilets. It sucks, but that's the way it is. Usually you're given a task, and if it's not done next week, maybe you're not as good as they thought.

Sorry, I'm serious. These are things I have picked up from 18 years in the industry.

Does anyone have any good advice on variable naming? Here's some of my rules I try to live by:

• camelCase
• use prefixes
• prefixes should be one word followed by an underscore.
• 10 character limit or 3 word limit, not counting the prefix
• functions should be prefixed with the file in which they're defined, ie utils_FooBar
• file names should be one word
• Start Bools with is
• Don't use not in bool names.
  • This has farther-reaching implications that will keep you from making confusing code most of the time (I'm sure this will be controversial, but it works no matter what they say)
• start output with _
• Globals should be g_VARIABLENAME
• use the least amount of words possible
• but being too verbose can draw attention - use this to aide in readability
  • calc_ImportantValueThatWillDecideTheUsersView is better than calc_SumYears if the variable is more important than the others.
• Even the greatest variable names are not replacements for documentation
• Even the most readable code is not replacement for documentation.
  • Force yourself to love documentation.

Edit: I realize I was speaking about function-naming with the prefix stuff.

For variables, I still use prefixes, but for variable type. Even if you define the variables as types, it's still incredibly useful. For instance,

a string is s_MyName,

enumerable is e_MyType,

A number is int or double or whatever i_MyAge or d_MyWeight

This might be obvious for custom objects, but I'd still do it like this p_Person or per_Person.

Seriously it does make a huge difference

I think the downvotes speak for themselves.

Agreed.