As someone who spends time programming, I of course find myself in conversations with people who aren’t as familiar with it. It doesn’t happen all the time, but these discussions can lead to people coming up with some pretty wild misconceptions about what programming is and what programmers do.

  • I’m sure many of you have had similar experiences. So, I thought it would be interesting to ask.
  • Fudoshin ️🏳️‍🌈
    link
    fedilink
    991 year ago

    “Just”

    That one word has done a fuck ton of lifting over my career.

    “Can’t you just make it do this”

    I can’t “just” do anything you fuck head! It takes time and lots of effort!

    • Skvlp
      link
      fedilink
      251 year ago

      Also “simple”. “It’s a simple feature.”

        • Skvlp
          link
          fedilink
          71 year ago

          I believe that it’s not for nothing that simplicity is considered more sophisticated. Many, many cycles of refinement.

        • Skvlp
          link
          fedilink
          171 year ago

          I worked in a post office once. I once had a customer demand some package delivery option, if I remember correctly. He was adamant that it was “only a few lines of code”, that I was difficult for not obliging, and that anyone in the postal service should make code changes like that on the whims of customers. It felt like I could have more luck explaining “wallpaper” to the currents in the ocean…

          • @catch22@startrek.website
            link
            fedilink
            71 year ago

            explaining “wallpaper” to the currents in the ocean…

            If this isn’t just a saying I haven’t heard of, I’m doing my best to make it a common place phrase, absolutely perfect in this context!

            • Skvlp
              link
              fedilink
              21 year ago

              Thank you so kindly :) It’s not a saying, as far as I know.

        • @Daedskin@lemm.ee
          link
          fedilink
          111 year ago

          I used to work on printer firmware; we were implementing a feature for a text box for if you scanned a certain number of pages on a collated, multi-page copy job. The text box told you it would print the pages it had stored to free up memory for more pages; after those pages had printed, another text box would come up asking if you wanted to keep scanning pages, or just finish the job.
          The consensus was that it would be a relatively simple change; 3 months and 80 files changed — with somewhere in the ballpark of 10000-20000 lines changed, — proved that wrong.

    • I like to say:

      We have a half finished skyscraper, and you’re asking me to Just add a new basement between the second and third floor. Do you see how that might be difficult? If we want to do it, we have to tear down the entire building floor by floor, then build up again from the second floor. Are you prepared to spend the money and push back the release date for that new feature?

    • @CaptDust@sh.itjust.works
      link
      fedilink
      6
      edit-2
      1 year ago

      “Just” is a keyword that I’m going to triple my estimates. “Just” signifies the product owner has no idea what they are requesting, and it always becomes a dance of explaining why they are wrong.

    • pinchcramp
      link
      fedilink
      51 year ago

      I would have written that comment if you hadn’t already done it.

      I don’t know exactly why people think that we can “just” do whatever they ask for.

      Maybe it has something to do with how invisible software is to the tech-illiterate person but I’m not convinced. I’m sure there are other professions that get similar treatment.

      • @CaptDust@sh.itjust.works
        link
        fedilink
        51 year ago

        I know you built the bridge to support 40 ton vehicles, but I think if we just add a beam across the middle here, we should be able to get 200 tons across this no problem? Seems simple, please have it done by Monday!

    • AwkwardLookMonkeyPuppet
      link
      fedilink
      English
      51 year ago

      I get that from our product owners a lot, and I usually say “yes!”, followed by an explanation of how much time it will take and why it’s not the path we want to take. People respond well to you agreeing with them, and then explaining why it’s probably not the best approach.