this post was submitted on 15 Jun 2023
35 points (100.0% liked)

Programmer Humor

32483 readers
509 users here now

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

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] johnhansarick@kbin.social 3 points 1 year ago (4 children)

Reminds me when I was working with a guy and he named a database table recieved . I had adapted my code to that, and then one day without warning he renamed it to received - and it took us an hour to figure out why everything broke.

[–] gbhorwood@kbin.social 0 points 1 year ago (2 children)

had a co-worker once who called the variable holding the first record in a complicated workflow "rec1st" and the last record "reclst", unaware that in every font used by every code editor except his, a lowercase l and number 1 look identical.

i spent a day debugging that after he quit.

[–] kartonrealista@lemmy.world 2 points 1 year ago

Lesson for the future: stop using crappy illegible fonts in a code editor, and use something nice like Fira Code or even Fira Mono or Sans if you don't like ligatures.

Edit: In the middle of writing this I realized it was a confusion between "1" and "l", which makes the font choice even more bizarre. What kinda garbage font doesn't distinguish between the two? I could understand if it was capital "i" and lowercase "l" since they look extremely similar in most sans serif fonts, but "1" and "l"?

Also it takes like 10 seconds to change the name of a variable across the whole file with a modern code editor like VSCode or an IDE for the specific language you were working with. If they were confusing you, you could have just changed "reclst" into "last_record" and that would save you a day of work.

[–] Bankenstein@feddit.de 1 points 1 year ago* (last edited 1 year ago)

No good code font would make 1 and l look identical. Character differentiability is like the most important thing.

Look, JetBrains did it right.

load more comments (1 replies)