• johnhansarick@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    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.

    • Black616Angel@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      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!

    • gbhorwood@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      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.

      • Bankenstein@feddit.deOP
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        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.