• FIST_FILLET@lemmy.ml
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    “prompt engineering” in itself is such an embarrassing term for the act of saying “computer uhhh show me epic boobies!!”

    like that joke about calling dishwashing “submerged porcelain technician” but unironically

    • frezik@midwest.social
      link
      fedilink
      arrow-up
      0
      ·
      9 months ago

      Yes, it is. Mostly because “real engineering” isn’t the high bar it’s made out to be. From that blog:

      Nobody I read in these arguments, not one single person, ever worked as a “real” engineer. At best they had some classical training in the classroom, but we all know that looks nothing like reality. Nobody in this debate had anything more than stereotypes to work with. The difference between the engineering in our heads and in reality has been noticed by others before, most visibly by Glenn Vanderburg. He read books on engineering to figure out the difference. But I wanted to go further.

      Software has developed in an area where the cost of failure is relatively low. We might make million dollar mistakes, but it’s not likely anybody dies from it. In areas where somebody could die from bad software, techniques like formal verification come into play. Those tend to make everything take 10 times longer, and there’s no compelling reason for the industry at large to do that.

      If anything, we should lean into this as an advantage. How fast can we make the cycle of change to deployment?

      • Alexstarfire@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        I help make Healthcare software. Mistakes can easily lead to death. Not most, but it’s something we always have to worry about.

      • ColeSloth@discuss.tchncs.de
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        9 months ago

        Realist, maybe. Often a pessimist. Never really a class traitor. Besides, I’m more blue collar than white collar, so I’ve never gotten the luxury of working from home at a higher pay, so as far as being the same class…in the sense of rich vs everyone else, sure.

        • Prunebutt@slrpnk.net
          link
          fedilink
          arrow-up
          0
          arrow-down
          1
          ·
          9 months ago

          Your snide comment just seemed a bit too glee about people about to lose their job. Or at least: lacking in solidarity with them.

          Forget the distinction between blue and white collar, or higher and lower income: these aren’t classes and the distinction onlyserves toseparateus in class struggle. I meant the “wage dependant class here”.

  • OsrsNeedsF2P@lemmy.ml
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    9 months ago

    Using an IDE isn’t programming either

    But I’ll definitely prefer hiring someone who does. Sure, you can code in Vi without plugins, but why? Leave your elitism at home. We have deadlines and money to make.

    Edit: The discussions I’ve had about AI here on Lemmy and Hackernews have seriously made me consider asking whether or not the candidate uses AI tools as an interview question, with the only correct answer a variation of “Yes I do”.

    Boomer seniors scared of new tools is why Oracle is still around. I don’t want any of those on my team.

    • frezik@midwest.social
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      Sure, you can code in Vi without plugins, but why? Leave your elitism at home. We have deadlines and money to make.

      Nothing elitist about it. Vim is not a modular tool that I can swap out of my mental model. Before someone says it, I’ve tried VS Code’s vim plugin, and it sucks ass.

    • dukk@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      AI’s not bad, it just doesn’t save me time. For quick, simple things, I can do it myself faster than the AI. For more big, complex tasks, I find myself rigorously checking the AI’s code to make sure no new bugs or vulnerabilities are introduced. Instead of reviewing that code, I’d rather just write it myself and have the confidence that there are no glaring issues. Beyond more intelligent autocomplete, I don’t really have much of a need for AI when I program.