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
    82
    arrow-down
    1
    ·
    11 months 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
        9
        ·
        edit-2
        11 months 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.)

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

    • 200ok@lemmy.world
      link
      fedilink
      arrow-up
      19
      ·
      11 months ago

      This one is the closest, IMO!

      Is it common knowledge that programmers write code in different “languages” (e.g. Java and C++)?

      • Hadriscus@lemm.ee
        link
        fedilink
        arrow-up
        5
        ·
        10 months ago

        My god, that’s terrible. Programmers from different countries must never understand each other. Someone should create a single programming language to rule them all ! something easy to understand, ideally -that everyone could read and write easily. Something like Espéranto, but with 1s and 0s

  • Sekrayray@lemmy.world
    link
    fedilink
    arrow-up
    48
    ·
    10 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.

  • xkforce@lemmy.world
    link
    fedilink
    arrow-up
    47
    ·
    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

    • spongebue@lemmy.world
      link
      fedilink
      arrow-up
      25
      ·
      10 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
        7
        arrow-down
        1
        ·
        10 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
    34
    ·
    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.

      • Lvxferre@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        10 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.

  • Linuto@lemmy.world
    link
    fedilink
    arrow-up
    30
    ·
    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
    28
    ·
    10 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