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)

  • Imgonnatrythis@sh.itjust.works
    link
    fedilink
    arrow-up
    44
    ·
    11 months 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.

      • pingveno@lemmy.ml
        link
        fedilink
        English
        arrow-up
        13
        ·
        edit-2
        11 months ago

        Yes, and under the hoodies there are t-shirts that were given out at conferences. That or memes. Strict.

  • xkforce@lemmy.world
    link
    fedilink
    arrow-up
    32
    ·
    11 months ago

    Reads code, spends too much time figuring out what it does and why the compiler is complaining about it, find out who wrote it, open drawer of voodoo dolls, rummage through them and pull out the relevant doll and stick another pin into it. A faint scream echoes through the cubicle farm. Place voodoo doll back in the drawer, close drawer, leave for lunch

  • Sekrayray@lemmy.world
    link
    fedilink
    arrow-up
    28
    ·
    11 months 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
    23
    ·
    11 months 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
      21
      ·
      11 months 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
        6
        ·
        11 months 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.

  • gothic_lemons@lemmy.world
    link
    fedilink
    arrow-up
    20
    ·
    11 months ago

    Well idk about all programming, but I imagine hackers go through at least one keyboard a month and suffer serious finger strain injuries from typing so fast and furious.

  • StereoTrespasser@lemmy.world
    link
    fedilink
    arrow-up
    21
    arrow-down
    3
    ·
    11 months 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
      2
      ·
      11 months 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!

      • Lvxferre@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        11 months 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.

  • MrVilliam@lemmy.world
    link
    fedilink
    English
    arrow-up
    18
    ·
    edit-2
    11 months ago

    A laughably small team is expected to do tasks that take triple the team size to do properly, and then the team gets endlessly shit on for Facebook looking different now for unrelated reasons while getting zero recognition for somehow finding a way to get some massive project done on an absurd timeline with no additional resources.

    I have been in power plants for many years now. Nobody notices us until we fuck up, and then nobody ever forgets. For example, Three Mile Island.

    • AMDIsOurLord@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      11 months ago

      A laughably small team is expected to do tasks that take triple the team size to do properly, and then the team gets endlessly shit on for Facebook looking different now for unrelated reasons while getting zero recognition for somehow finding a way to get some massive project done on an absurd timeline with no additional resources.

      You already have the latter 5 year portion of what you learn in your first 10 years as a computer scientist

      Now you just need the first 5 years of education

  • Linuto@lemmy.world
    link
    fedilink
    arrow-up
    18
    ·
    11 months ago

    Swinging between feeling like you’re a computer god, and then feeling like you’re horrible at your job.

  • Skotimusj@lemmy.ml
    link
    fedilink
    arrow-up
    17
    ·
    11 months 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