• Addv4@kbin.social
    link
    fedilink
    arrow-up
    39
    ·
    10 months ago

    That if you know how to code, you understand how computers work and understand really complicated math concepts.

    • BrianTheeBiscuiteer@lemmy.world
      link
      fedilink
      arrow-up
      14
      ·
      10 months ago

      That’s the difference between a programmer and a computer scientist, but even I (a computer scientist) I’m not an expert in hardware, networking, or OS level operations because that’s not my daily focus.

      • Landless2029@lemmy.world
        link
        fedilink
        arrow-up
        11
        ·
        10 months ago

        I compare my career to the medical field. Sure there are some crossovers but lots of specialties.

        Would you consult a dentist about your bowel movements?

      • cole@lemdro.id
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        and what you just described is the difference between a computer scientist and a computer engineer!

    • jadero@programming.dev
      link
      fedilink
      arrow-up
      6
      ·
      10 months ago

      I call that the “nerd equivalency problem”. I think it’s the source of much (most? all?) of the problems with software that comes out of organizations that are not programming shops by nature.

      “We’re not moving fast enough (or, “I have this great idea!”), hire another nerd!”

      The problem also exists within individual programmers (“sure, I can do that UX/UI thingy, just let me finish building this ray-tracing thingy”), but that’s just an ordinary cognitive weakness that affects us all (thinking that being expert in one field makes one expert in all). It’s the job of proper leadership to resist that, not act as though it’s true.