I’ve always been curious as to what “normal” people think programming is like. The wildest theory I’ve heard is “typing ones and zeroes” (I’m a software engineer)

  • OurTragicUniverse@kbin.social
    link
    fedilink
    arrow-up
    76
    arrow-down
    1
    ·
    1 year ago

    It involves a lot of tall girls in thigh high socks, sometimes they wear cat ears too. And they do a lot of typing on extra clackity keyboards.

      • OurTragicUniverse@kbin.social
        link
        fedilink
        arrow-up
        6
        arrow-down
        7
        ·
        edit-2
        1 year ago

        Don’t be a bigot. Tall girls are awesome.

        *(Also in case you weren’t being a bigot and were instead referring to what it’s really like to work in tech: I do know industry isn’t entierly cat girls in coding socks but most of the computers for career people I’ve known have been, so I choose to believe.)

  • Sekrayray@lemmy.world
    link
    fedilink
    arrow-up
    48
    ·
    1 year ago

    It’s like building the NY subway system—you’re constantly adding on new bypasses and trying to maintenance old tunnels in order to account for new features/population. It ultimately ends up working most of the time and the daily commuters get to move from Point A to Point B with minimal interruption, but if you viewed the subway as a whole it’s a cobbled mess with lots of redundancy. Some of the architects who are currently around don’t even know where the oldest tunnels go, or why they’re there.

    Wanted to give a take on it that didn’t focus on the obvious “language” aspect. I could be 100% wrong on this—I’m sort of basing it off of comments I’ve seen here or there. I know very few folks who work in tech and I work in healthcare.

  • TIMMAY@lemmy.world
    link
    fedilink
    arrow-up
    39
    ·
    1 year ago

    I think its like trying to get a toddler to accomplish a task and it keeps technically doing what you said but in an annoying and counterproductive way you didnt even think of yet and you have to just become insanely specific about what you want the toddler to do and when and in what order with what timing

    • spongebue@lemmy.world
      link
      fedilink
      arrow-up
      25
      ·
      1 year ago

      That’s actually really accurate when first learning to program. Eventually you figure out how to think like a toddler.

      • NotMyOldRedditName@lemmy.world
        link
        fedilink
        arrow-up
        7
        arrow-down
        1
        ·
        1 year ago

        But then you gotta deal with the teenagers.

        You tell them exactly what to do, and they do most of the time, but they can twist words and meanings to come up and do something entirely different when it suits their needs.

  • Imgonnatrythis@sh.itjust.works
    link
    fedilink
    arrow-up
    37
    ·
    1 year ago

    That sounds ridiculous. It 2024, I’m pretty sure programmers just use voice input and say the ones and zeros instead of sitting there and doing all that typing. Still not sure why they have to wear black hoodies though.

      • Lvxferre@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        I meant “decrypted”, not “decompiled”. (When I wrote the above I was sleep-deprived.)

        I mostly pick visual novels apart, to know how to reach one or another specific route. From that I’m somewhat used to read Python code - or at least Ren’Py code.

  • Skotimusj@lemmy.ml
    link
    fedilink
    arrow-up
    28
    ·
    1 year ago

    I would imagine it is as follows:

    1. Come up with ideas or goal to accomplish /be given said goal

    2. spend large amount of time looking at existing code or prior implementation of your stated goal.

    3. attempt to write or import some code tailored to your specific needs

    4. test and identify problem areas

    5. find everything fails spectacularly and start over +/- tears.

    6. repeat until successful or dead

  • StereoTrespasser@lemmy.world
    link
    fedilink
    arrow-up
    26
    arrow-down
    5
    ·
    1 year ago

    Judging by the amount of their nonsense posted on Lemmy, I imagine programmers sitting around all day creating memes about how hard their job is.

    Seriously, this is the most Lemmy-ish post I have ever seen. “I see there are people not in programming discussing non-programming topics…what question can I ask to steer the question back to programming?”

    • 𝕽𝖔𝖔𝖙𝖎𝖊𝖘𝖙@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Judging by the amount of their nonsense posted on Lemmy, I imagine programmers sitting around all day creating memes about how hard their job is.

      Programmers are just like the rest of us!

  • HipsterTenZero@dormi.zone
    link
    fedilink
    arrow-up
    21
    ·
    1 year ago

    Imagine a poorly lit room. The smell of coffee permeates every inch while the Baba is You soundtrack is played on repeat. Five to fifty monkeys sit in desks and attempt to bind whatever devils are necessary to invoke the magic their leader demands. sixty three percent of their effort is actually just browsing social media and posting memes in niche online communities, but they still manage to get stuff done.

  • FollyDolly@lemmy.world
    link
    fedilink
    arrow-up
    14
    ·
    1 year ago

    You guys talk to computers in the language of computers. You are trying to get the computer to do something you want. However the computer doesn’t help you out, you have to tell it explicitly what to do down to the tinyist detail or it won’t work and you will be sad.

    To the outside observer this looks like typing gibberish and copying in chunks of more gibberish. With occasional swearing.

    How’d I do? (I know very little about programming and computers, I’ve worked manual labor for something like 20 years.)

    • CanadaPlus@futurology.today
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      That’s pretty much bang on.

      You learn pretty fast that you’re an idiot and yes, you can write something, read it back many times, and still be wrong.

        • CanadaPlus@futurology.today
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 year ago

          With that one, at least your parser should crap itself right around where the error is. You probably just need to search engine the error message, and find the page every other noob has to. Then it won’t take too long.

          If your thing compiles but doesn’t work, then the real fun begins. You’re in the magical land of Turing completeness, where you hope the problem isn’t unsolvable in your case, because it definitely is in general.