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)

  • nicerdicer@feddit.deEnglish
    0·
    10 months ago

    I think programming can be a pretty dull task, where you spend hours over hours copy-pasting fragments of code from former projects and/or from other sources, adjust it to your needs, run it, remove the bug, run it again and find the new ten bugs over and over again.

    But you get to wear a black hoodie and a mask.

  • driving_crooner@lemmy.eco.br
    0·
    10 months ago

    What about us who are not in the IT industry but our job is being programmers (I’m an actuarie, on the insurance industry, and I spend 90% of my time programming scripts on python and SQL)

  • southsamurai@sh.itjust.works
    0·
    10 months ago

    Well, I’m not really the truly blind here, I used to do some BASIC back in the eighties. Just introductory level shit, though. I’m talking a course taken over a summer for “gifted” kids, not even an actual full on course at a serious level. And I wasn’t very good at it lol

    But, I still have no clue what modern languages are like, or how they’re used professionally. I’ve always assumed, you guys are busy entering lines of code, then compiling and testing, then punching things because you have to go back and fuck up with the code again.

    I figure there may be ways to streamline the coding itself, maybe chunks of prefab that can be copy/pasted, or whatever.

    Other than that, I suppose there’s lots of coffee, coke and/or meth, and a lot of waifu pillows.

    • Shdwdrgn@mander.xyzEnglish
      0·
      10 months ago

      Imagine this… line numbers are no longer a thing. 😆 Yeah I learned programming in the 80’s as well, the Sinclair ZX81 was my first computer. These days a large number of languages, both compiled and parsed, are based around C so it’s pretty easy to jump around a lot.

      • southsamurai@sh.itjust.works
        0·
        10 months ago

        Okay, no line hikers numbers. But, how the hell are things carried out in order? Did numbering just get replaced by another system, or did it get thrown out as unnecessary to coding as a whole?

        • Shdwdrgn@mander.xyzEnglish
          0·
          10 months ago

          Yeah line numbers got thrown out as a whole. Code is still followed in sequential order, but instead of GOTO we now have functions that we call for reusable operations, and those functions can have parameters sent to them. So like you can set up a function that adds a line of text to a log file, then call the function with a variable containing that text. I honestly can’t remember if we had something like that in the early versions of BASIC. Overall I felt it made things a lot easier when line numbers were dropped, especially when you wanted to add more code in the middle of an existing block so you weren’t forced to renumber everything to make room.

          I think the biggest change to wrap my head around was the elimination of the GOTO statement. This seemed like such a mistake at first, but it turns out that if you wrap things within conditional expressions (if-then and do-while are typical) then you really don’t need GOTO jumping all over the place and it tends to keep specific operations more self-contained which leads to the code being easier to read through.

          If you want to see some examples of more modern code, take a look at something for PHP. This code felt most at home to me when I moved away from BASIC and is one of the few that still uses the $ symbol to denote variable names. Loops and conditionals are enclosed in {curly braces} so instead of the old for i$=1 to 5:<code here>:next loop you would see something like for($i=1; $i<=5; $i++){<code here>} and you just add as many lines as you need in between them. This is where indenting your code became popular, because if you have a lot of nested conditionals/loops it’s easy to lose your place. The indents give you a reference of which code is part of which loops. Overall things have changed quite a bit, but at the core of it your code is still following a specific order to get things done.

  • RuBisCO@slrpnk.net
    0·
    10 months ago

    When things get really tough, two of you will double up on the same keyboard.

    1 in 6 have multiple personalities and substance abuse daemons.

    Your bosses ride little skateboards everywhere, when they’re not busy programming animated singing viruses.

    The FBI watches you code, but has no idea what they’re looking at.

    A significant fraction of you can type with your feet, proficiently.

  • monsterlynn@kbin.social
    0·
    10 months ago

    @httpjames Back in the day I liked to dabble in Linux, and I always liked the IT people in the larger firms I worked at so I imagine it’s understanding basics of code, and then a lot of googling for fixes to problems people have already dealt with, composting code with templates and tweaking it to work with the specifics of the job at hand and then taking credit for saving everything because people are dumb.

  • Imgonnatrythis@sh.itjust.works
    0·
    10 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.