this post was submitted on 17 Nov 2023
39 points (100.0% liked)

Programming

423 readers
5 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] onlinepersona@programming.dev 5 points 1 year ago (6 children)

I agree with part of the article, because I didn't read the rest. I truly dislike the use of single letter variable names: f, g, h and foo, bar, baz. My advice: use descriptive variable names.

function twoIfs, function complicatedIf, var simpleAnd, etc. Makes it so much easier to read examples instead of remembering "oh yeah, f had two ifs in it, h had the if/else, g calls f which calls h which,...".

Also see this often in other examples: "A for 'Truthy variable' " ๐Ÿ˜“ Wtf. Laziness is good when it makes things easier, not harder.

[โ€“] lysdexic@programming.dev 3 points 1 year ago (5 children)

My advice: use descriptive variable names.

The article is really not about naming conventions.

[โ€“] Sheldan@programming.dev 9 points 1 year ago (3 children)

Should have still used them. It was harder to read this way.

[โ€“] potterman28wxcv 1 points 1 year ago

Agreed that some people can find it easier with explicit names - however some people find it easier with short meaningless names as it makes them focus on the abstraction rather than the naming. There is no right or wrong here. It all depends on the reader.

load more comments (2 replies)
load more comments (3 replies)
load more comments (3 replies)