718
you are viewing a single comment's thread
view the rest of the comments
[-] kevincox@lemmy.ml 19 points 6 months ago

To be fair having a name can make things easier to read. I get that i % 2 == 0 is a common pattern and most programmers will quickly recognize what is happening. But isEven(i) is just that much easier to grok and leaves that brainpower to work on something else.

But I would never import a package for it. I would just create a local helper for something this trivial.

[-] NotAViciousCyborg@lemmy.world 10 points 6 months ago

Exactly what I would do if I had to reuse it, especially now since I know that adding a package would actually add 2. It all just seems so...inefficient

[-] kevincox@lemmy.ml 11 points 6 months ago

Even if the code isn't reused adding names to sub-expressions can be very valuable. Often times I introduce new functions or variables even if they are only used once so that I can give them a descriptive name which helps the reader more quickly understand what is happening.

[-] NotAViciousCyborg@lemmy.world 3 points 6 months ago

Yeah, I do that with pretty much every separate operation in c# since our solutions are pretty big. Most of my JS scripts are just done in ServiceNow which are separated and named appropriately.

this post was submitted on 21 Apr 2024
718 points (97.0% liked)

Programmer Humor

32380 readers
836 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS