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.
Our Python virtual environments at work on all Linux-servers are in the directory /opt/vens instead of /opt/venvs so when some intern corrects that, we will be screwed!
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.
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.
This reminds me of the HTTP referer header, which started as a misspelling of referrer, but because everyone just went with it is now part of the standard.
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 toreceived- and it took us an hour to figure out why everything broke.Our Python virtual environments at work on all Linux-servers are in the directory /opt/vens instead of /opt/venvs so when some intern corrects that, we will be screwed!
I’ve had the misfortune to work with a database containing both spellings across various tables. Some tables would have both in different columns
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.
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.
No good code font would make
1andllook identical. Character differentiability is like the most important thing.Look, JetBrains did it right.
This reminds me of the HTTP referer header, which started as a misspelling of referrer, but because everyone just went with it is now part of the standard.