Serious question. We had a perfectly serviceable word, yet everyone decided to shift. Is it just that it’s shorter to type?

If so, I feel for your colleagues trying to parse your code when all your variables use abbreviations.

  • James R Kirk@startrek.website
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    10 hours ago

    This is a guess but I feel like it was around the time that most coding was done for things that weren’t explicitly “programs”, like web design CSS/Java and smartphone “apps”.

    • maegul (he/they)@lemmy.ml
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      10 hours ago

      Yea this vibes.

      For me, it felt like coding was a more attractive term for people who weren’t “proper” computer science and “engineering” types who weren’t confident that they knew what “program” meant or even “algorithm”, as they were working things as they went.

      I’d guess that as computing involved more and more people with this non-standard background, coding became preferred. I certainly encountered people uncomfortable with my casual use of “algorithm” because it triggered their imposter syndrome, and my pointing out that they write algorithms with the code the write all the time certainly didn’t help.

    • masterspace@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 hours ago

      Also anyone writing scripts, or even just using stuff like AWS Lambda / functions as a service, etc. etc.