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.
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.
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.
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!
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.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.
No good code font would make
1
andl
look identical. Character differentiability is like the most important thing.Look, JetBrains did it right.
Maybe he wasn’t really unaware that only his font choice differentiated the names.
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.
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!